[tor-bugs] #2356 [Tor Bridge]: Clarification of the ReachableAddresses option
Tor Bug Tracker & Wiki
torproject-admin at torproject.org
Thu Apr 28 23:00:20 UTC 2011
#2356: Clarification of the ReachableAddresses option
------------------------+---------------------------------------------------
Reporter: anonym | Owner: arma
Type: defect | Status: assigned
Priority: major | Milestone: Tor: 0.2.2.x-final
Component: Tor Bridge | Version: Tor: 0.2.1.26
Keywords: | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by arma):
When I reproduce all of this leaving Vidalia out of the loop, it works as
expected:
{{{
Apr 28 18:50:43.884 [notice] Bridge at '188.x.x.x:443' isn't reachable by
our firewall policy. Skipping.
}}}
When I use Vidalia to set the bridge, it looks like Vidalia is doing a
resetconf on our reachableaddresses config option.
Before:
{{{
getconf reachableaddresses
250 ReachableAddresses=reject *:*
}}}
After:
{{{
getconf reachableaddresses
250 ReachableAddresses
}}}
To be fair, I bet your Vidalia settings don't have "My firewall only lets
me connect to certain ports" clicked. So you have told Vidalia that you
can reach all addresses. Not totally crazy that it would correct your Tor
to match your Vidalia settings.
When I click the "My firewall only lets me connect to certain ports" and
set it to 1, I get the behavior you wanted.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2356#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list