[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-talk] Problem with new multiple-instance exit nodes never showing up in directory (cached consensus)

To: tor-talk@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-talk] Problem with new multiple-instance exit nodes never showing up in directory (cached consensus)
From: Moritz Bartl <moritz@xxxxxxxxxxxxxx>
Date: Fri, 27 Jul 2012 16:45:58 +0200
Delivered-to: archiver@xxxxxxxx
Delivery-date: Fri, 27 Jul 2012 16:43:12 -0400
In-reply-to: <CAPNSmRoPav8wA+cXpC3697=FMH0K5enWKKRj6Ti5aEm0SWccFA@xxxxxxxxxxxxxx>
List-archive: <http://lists.torproject.org/pipermail/tor-talk>
List-help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-id: "all discussion about theory, design, and development of Onion Routing" <tor-talk.lists.torproject.org>
List-post: <mailto:tor-talk@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
References: <500DCEEC.9030006@xxxxxxxxxxxxxxx> <500DCF32.3010302@xxxxxxxxxx> <FC899264-2C31-4672-AE20-0B9073216FC0@xxxxxxxxx> <20120724081912.GA4703@xxxxxxxxxxxxxxxx> <5011AB3D.9000702@xxxxxxxxx> <CABqy+sp5feQLFZ2DcN8hv_zT6_xDKpjAwLm59c=nLHB1oGt0Kw@xxxxxxxxxxxxxx> <CAPNSmRoPav8wA+cXpC3697=FMH0K5enWKKRj6Ti5aEm0SWccFA@xxxxxxxxxxxxxx>
Reply-to: tor-talk@xxxxxxxxxxxxxxxxxxxx
Sender: tor-talk-bounces@xxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0

On 27.07.2012 05:48, Name Withheld wrote:
> For B), this is probably a total newbie question, since I've never had to
> run a program like this before.  If I can get a second IP from the ISP for
> the same physical server, is there a configuration option in Debian (or
> something in the torrc file) I'll need to set to get it to the additional
> tor daemons binding to the secondary address?

Use *Address to bind your Tor to your second addres. From
http://www.torservers.net/misc/config/torrc :

ORPort 443
DirPort 80
Address 109.163.233.200
OutboundBindAddress 109.163.233.200
ORListenAddress 109.163.233.200:443
DirListenAddress 109.163.233.200:80

DataDirectory /var/lib/tor/0
PidFile /var/run/tor/tor0.pid
Log notice file /var/log/tor/notices0.log

-- 
Moritz Bartl
https://www.torservers.net/
_______________________________________________
tor-talk mailing list
tor-talk@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Follow-Ups:
- Re: [tor-talk] Problem with new multiple-instance exit nodes never showing up in directory (cached consensus)
  - From: Name Withheld

References:
- [tor-talk] Fwd: [liberationtech] FFII - European Commission net neutrality consultation excludes TOR users
  - From: SiNA Rabbani
- Re: [tor-talk] Fwd: [liberationtech] FFII - European Commission net neutrality consultation excludes TOR users
  - From: Runa Sandvik
- Re: [tor-talk] Fwd: [liberationtech] FFII - European Commission net neutrality consultation excludes TOR users
  - From: andrew
- [tor-talk] Problem with new multiple-instance exit nodes never showing up in directory (cached consensus)
  - From: Name Withheld
- Re: [tor-talk] Problem with new multiple-instance exit nodes never showing up in directory (cached consensus)
  - From: Robert Ransom
- Re: [tor-talk] Problem with new multiple-instance exit nodes never showing up in directory (cached consensus)
  - From: Name Withheld

Prev by Author: Re: [tor-talk] [Need quick help] 30+ mbps node taken down by host
Next by Author: Re: [tor-talk] [Need quick help] 30+ mbps node taken down by host
Previous by thread: Re: [tor-talk] Problem with new multiple-instance exit nodes never showing up in directory (cached consensus)
Next by thread: Re: [tor-talk] Problem with new multiple-instance exit nodes never showing up in directory (cached consensus)
Index(es):
- Author
- Thread