This seems to work. The view from Vidalia's Message Log:
[Notice] Learned fingerprint 24432B99CA2533BC95ABF66C7AFE835F96DD2B2D for bridge 2a00:1d70:ed15:37:235:53:64:0:443 [Notice] no known bridge descriptors running yet; stalling [Notice] Bridge 'Unnamed' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address (2a00:1d70:ed15:37:235:53:64:0:443). [Notice] new bridge descriptor 'Unnamed' (fresh): $24432B99CA2533BC95ABF66C7AFE835F96DD2B2D~Unnamed at aa.bb.cc.dd [Notice] We now have enough directory information to build circuits. [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
This is a snippet of my Tor config file:
Address [2a00:1d70:ed15:37:235:53:64:0] OutboundBindAddress aa.bb.cc.dd ORPort [2a00:1d70:ed15:37:235:53:64:0]:443 ORPort [aa.bb.cc.dd]:443
Note #1: I'm specifying the IPv4 address explicitly because my server has 2 network interfaces.
Note #2: I am using the IPv4 address for OutboundBindAddress because this config option seems not to understand IPv6 addresses.
Thanks for the advice.
On 09/18/2012 07:29 AM, Linus Nordberg wrote:
You're right. Brackets are not significant.
The 'NoAdvertise' is the other piece of bad advice I've been giving. You will have to remove that flag and really run your bridge on the IPv4 address as well as the IPv6 for now. Or filter it off in a local firewall or something like that outside of Tor.