ReachableAddresses ignored when playing with bridges using Vidalia
I think this possible bug is best illustrated with an example. I do this using Tor 0.2.1.28 (not currently present in Version list) and Vidalia 0.2.10:
-
I clear the Tor data dir ("rm /var/lib/tor/*" in my case) and add "ReachableAddresses reject :" to torrc.
-
I start Tor. ReachableAddresses prevents it from bootstrapping as expected.
-
I start Vidalia and add a bridge. Tor immediately bootstraps and all connections to the Tor network are made through the bridge (verified with packet sniffer) as expected (except that the bridge connection is exempt from ReachableAddresses, see ticket #2356 (moved)).
-
I restart Tor. Tor hangs on "Bootstrapping 85%" according to the log, accompanied by the notices:
Notice: no known bridge descriptors running yet; stalling
and
Notice: Our directory information is no longer up-to-date
enough to build circuits: No live bridge descriptors.
What's Tor's problem with the bridge (I have verified that the bridge works on another system)?
- I disable bridges in Vidalia. Now Tor immediately bootstraps by connecting directly to the Tor network, ignoring the ReachableAddresses options still present in torrc. I have verified that the connection is direct using a packet sniffer.
Why is ReachableAddresses suddenly ignored?
- I restart Tor and Vidalia (bridges still off). Tor still connects to the Tor network, ignoring ReachableAddresses.
Again, why is ReachableAddresses suddenly ignored?
- I stop Tor and Vidalia, clear Tor's data dir, and then start Tor and Vidalia (again, no bridges). Now the behaviour is the same as in point 2 and everything works as expected.
But why does clearing the Tor data dir make a difference?
Here's the original post about this issue on the T(A)ILS development mailing list, but I think all relevant information is posted above: http://article.gmane.org/gmane.linux.distributions.tails.devel/83