#20154: If you specify a exit node you can not connect to url that contain the
port
number
--------------------------------------+---------------------------
Reporter: qqqqw | Owner: tbb-team
Type: defect | Status: closed
Priority: Medium | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution: not a bug
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------+---------------------------
Changes (by dcf):
* status: new => closed
* resolution: => not a bug
Comment:
Thanks for reporting this. In this case, while it might be surprising, Tor
Browser is only doing what you instructed.
Every exit node has an "[[doc/ReducedExitPolicy|exit policy]]" that says
what destinations and ports it is willing to connect to. An exit policy
that only allows access to ports 22, 80, and 443 would look like this:
{{{
accept *:22
accept *:80
accept *:443
reject *:*
}}}
It must be that the exit node you chose does not allow access to port 182.
Tor cannot build a circuit that violates the exit policy, so it gives up.
When you remove your ExitNodes setting, Tor is free to choose a different
exit node, one that ''does'' allow access to port 182, which is why Tor
works in that case. When you omit the port number, Tor Browser uses the
default port number 80, which is allowed by almost all exits.
You can check the exit policy of your chosen exit node by searching for it
at https://atlas.torproject.org/. If the exit does not allow the port you
want, there's nothing you can do—you have to choose a different exit.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20154#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
