[tor-relays] Call for obfs4 bridges, and a brief discussion of obfs4proxy.

Steve Snyder swsnyder at snydernet.net
Tue Oct 28 03:33:33 UTC 2014



On 10/27/2014 06:38 PM, s7r wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> On 10/28/2014 12:24 AM, Steve Snyder wrote:
>> Does obfs4 support IPv6 addresses?  If so, does it work like ORPort
>> in that it is just a matter of adding another line?
>>
>>
> Yes.
>
>> For example, to add an IPv6 address can I just replace
>>
>> ServerTransportListenAddr obfs4 111.222.333.444:__RNDPORT__
>>
>> with
>>
>> ServerTransportListenAddr obfs4 111.222.333.444:__RNDPORT__
>> ServerTransportListenAddr obfs4
>> [1111:2222:3333:4444::1]:__RNDPORT__
>>
>> in the config file?
>>
> Yes, that sounds right. If you don't have multiple interfaces or don't
> care if you open the ports on all interfaces, here is how I do it:
> I use ServerTransportListenAddr obfs4 [::]:_RNDPORT_ -> it opens the
> obfuscated ports on both v4 and v6 (dual stack).
>
> If you do so, do it to ORPort also, so it will be a fully dual stack
> bridge, like:
> ORPort 111.222.333.444:_PORT_
> ORPort [111.222.333.444::1]:_PORT_
>
>> Can I use the same ExtORPort for both IPv4 and IPv6 addresses?
>>
> Just use
>
> ExtORPort auto

See, the problem is that I *do* have multiple interfaces, each with an 
IPv4 and IPv6 address.  I don't go the "auto" route because I want to 
avoid having Tor pick the wrong interface/addresses.  I want the bridge 
to run on a given interface and only on that interface.

One more question: how can I test the functionality of obfs4proxy given 
that TorBrowser v4.0.0 doesn't support this transport?

Thanks for the response.


More information about the tor-relays mailing list