Automatically chosen published ports should be stable

Tor 0.2.2.x adds the ability to configure ports with "FooPort auto", and get Tor to choose a port on its own. However, these ports will almost certainly not be the same across invocations of Tor, which makes them unsuitable for ORPort and DirPort usage.

Tor should record the values chosen for published (that is, ORPort and DirPort) "auto" ports, and try to reuse them in later invocations. Of course, if those ports aren't available, it'll need to choose a new port anyway.

changed milestone to %Tor: unspecified

added component::core tor/tor configuration intro milestone::Tor: unspecified owner::blackpaw points::4 ports priority::high severity::normal small-feature stability status::assigned tor-relay type::enhancement labels

Trac:
Description: Tor 0.2.2.x adds the ability to configure ports with "FooPort auto", and get Tor to choose a port on its own. However, these ports will almost certainly be the same across invocations of Tor, which makes them unsuitable for ORPort and DirPort usage.

Tor should record the values chosen for published (that is, ORPort and DirPort) "auto" ports, and try to reuse them in later invocations. Of course, if those ports aren't available, it'll need to choose a new port anyway.

to

Tor 0.2.2.x adds the ability to configure ports with "FooPort auto", and get Tor to choose a port on its own. However, these ports will almost certainly not be the same across invocations of Tor, which makes them unsuitable for ORPort and DirPort usage.

Tor should record the values chosen for published (that is, ORPort and DirPort) "auto" ports, and try to reuse them in later invocations. Of course, if those ports aren't available, it'll need to choose a new port anyway.

See also #3948 (moved)

We should really do this, but I don't see it happening as a small feature before the deadline. But in 0.2.4.x, for sure!

Trac:
Milestone: Tor: 0.2.3.x-final to Tor: 0.2.4.x-final

Trac:
Keywords: N/A deleted, tor-relay added

Trac:
Component: Tor Relay to Tor

I'd love to have this if anybody can hack it before the deadline.

Trac:
Keywords: tor-relay deleted, tor-relay small-feature added

Trac:
Milestone: Tor: 0.2.4.x-final to Tor: 0.2.5.x-final

I can do this, since no one else will for a long time. One has to start somewhere.

Trac:
Username: blackpaw
Status: new to assigned
Owner: N/A to blackpaw

Trac:
Milestone: Tor: 0.2.5.x-final to Tor: 0.2.???

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

Trac:
Sponsor: N/A to N/A
Severity: N/A to Normal

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

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

Trac:
Milestone: Tor: 0.3.??? to Tor: unspecified
Keywords: tor-relay small-feature deleted, tor-relay, small-feature, tor-03-unspecified-201612 added

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Priority: Medium to High
Keywords: N/A deleted, ports, configuration, intro, stability added
Reviewer: N/A to N/A
Points: N/A to 4

changed time estimate to 32h

mentioned in issue #3948 (moved)

mentioned in issue #13920 (moved)

moved to tpo/core/tor#3511 (closed)

mentioned in issue tpo/core/tor#3948 (closed)