Opened 6 years ago

Last modified 4 months ago

#3948 new enhancement

"fooport auto" should be able to get a hint

Reported by: arma Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-relay configuration state needs-design
Cc: erinn, alan.hamlett@…, tor+trac@… Actual Points:
Parent ID: Points: 4
Reviewer: Sponsor:

Description (last modified by arma)

In #3945 we learned that "socksport auto" (as implemented in #3076) on Windows is confusing users who use external applications that expect Tor to be listening on port 9050. The "fix" was to disable using auto ports in the TBB 0.2.2 Windows bundles.

A better answer to this issue is to

A) teach Tor how to remember which port it used last time, and try that one first (#3511)

B) seed it with our favorite port, e.g. by setting another config option like "SocksPortPreferred 9050". Maybe it would try both the preferred port and the one it picked last time, in some order. My first thought is that it should try the previous one first, and fall back to the configured preference before falling back to a random high-numbered port.

If we want to get fancier, we could make the prefered list be a 'schedule' of ports to try, e.g. for ORPortPreferred it could be "443,80".

Picking a more normal port should also help the Comodo firewall users in #3941 who are being blocked from reaching their high-numbered port.

Child Tickets

Change History (18)

comment:1 Changed 6 years ago by arma

Cc: erinn added

comment:2 Changed 6 years ago by nickm

Part (A) above is, I think, the same as bug #3511.

comment:3 Changed 6 years ago by arma

Description: modified (diff)
Summary: "fooport auto" should be able to get a hint, and should try to pick a consistent port"fooport auto" should be able to get a hint

Right you are! Pruning this one so it is more clearly part (B).

comment:4 Changed 6 years ago by nickm

Milestone: Tor: 0.2.3.x-finalTor: 0.2.4.x-final

Too tricky and fragile to be workable for 0.2.3 imo.

comment:5 Changed 6 years ago by ahamlett

Cc: alan.hamlett@… added

This is related to #4182.

comment:6 Changed 5 years ago by nickm

Keywords: tor-client added

comment:7 Changed 5 years ago by nickm

Component: Tor ClientTor

comment:8 Changed 5 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: 0.2.5.x-final

comment:9 Changed 4 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.6.x-final

comment:10 Changed 3 years ago by nickm

Keywords: 026-triaged-1 added

comment:11 Changed 3 years ago by nickm

Milestone: Tor: 0.2.6.x-finalTor: 0.2.???

comment:12 Changed 3 years ago by StrangeCharm

Cc: tor+trac@… added

comment:13 Changed 22 months ago by teor

Severity: Normal

This also affects relays with bandwidth accounting active: whenever the bandwidth period rotates, they change ports, even if they didn't hibernate.

comment:14 Changed 10 months ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:15 Changed 9 months ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:16 Changed 4 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:17 Changed 4 months ago by nickm

Keywords: 026-triaged-1 removed

comment:18 Changed 4 months ago by nickm

Keywords: tor-relay configuration state needs-design added; tor-client removed
Points: 4
Priority: HighLow
Note: See TracTickets for help on using tickets.