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

Re: [tor-relays] SocksPort flags trouble

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-relays] SocksPort flags trouble
From: Nick Mathewson <nickm@xxxxxxxxxxxxx>
Date: Wed, 11 Jul 2012 11:33:52 -0400
Delivered-to: archiver@xxxxxxxx
Delivery-date: Wed, 11 Jul 2012 11:33:26 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=M8/fvvjuOc8V7MOt7xqY2REhiLhLyFdv305ptee1NRM=; b=sOGEQYkkW+3QyedXTwAHzcu3XbdvV+FHU5XaC78snmF1jTBXmALmdsD83iWFbDBE35 5fxAg5YezIzce62UqTQY4bISDwTnz2w2NwpqiGO8mA8CdCsEg9KeV6eNF2/YxsqvTpzi u/6fpct4kvag9SRmAZJAsw3Rr/R6pShZ4zJffNDbzhxqOvBQCFZm6H5+QW2pIzxEJ0uL gczgrcRWcu1Cs/xq0ANeRv7a6NvCstwQFalFCsKpv4Me3UgbRcLR8Q5VVVXwefcjJGJ3 F1RYO6hP5SD/0UoIFdGBOmene2Thu/qztsQEZmMQwN1cfiom5Hr4rmuu/abQyw0jLcRB PR7g==
In-reply-to: <201207080819.q688J8vB018197@xxxxxxxxxxxxx>
List-archive: <http://lists.torproject.org/pipermail/tor-relays>
List-help: <mailto:tor-relays-request@lists.torproject.org?subject=help>
List-id: "support and questions about running Tor relays \(exit, non-exit, bridge\)" <tor-relays.lists.torproject.org>
List-post: <mailto:tor-relays@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=unsubscribe>
References: <201207080819.q688J8vB018197@xxxxxxxxxxxxx>
Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx
Sender: tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx

On Sun, Jul 8, 2012 at 4:19 AM, Scott Bennett <bennett@xxxxxxxxxx> wrote:
>      While testing my torrc with 0.2.3.18-rc, I tried adding the
> IsolateDestAddr flag to the SocksPort line, as in
>
> SocksPort 9050 IsolateDestAddr
>
> A "tor --verify-config" claimed that I was trying to specify more
> than one port on that line, which would be an error.  Are the SocksPort
> flags listed in the tor man page for 0.2.3.18-rc not yet implemented?

Just tried it with 0.2.3.18-rc (as tagged in git), using only that
option.  It worked for me.  Could you have had some other tor in your
path as "tor", or something like that?

yrs,
-- 
Nick
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Follow-Ups:
- Re: [tor-relays] SocksPort flags trouble
  - From: Fabio Pietrosanti (naif)

References:
- [tor-relays] SocksPort flags trouble
  - From: Scott Bennett

Prev by Author: Re: [tor-relays] Call for discussion: turning funding into more exit relays
Next by Author: Re: [tor-relays] SocksPort flags trouble
Previous by thread: [tor-relays] SocksPort flags trouble
Next by thread: Re: [tor-relays] SocksPort flags trouble
Index(es):
- Author
- Thread