[tor-bugs] #25182 [Core Tor/Tor]: systemd unit file starts Tor before IPv6 address is available

[Tor Bug Tracker & Wiki]

#25182: systemd unit file starts Tor before IPv6 address is available
--------------------------+------------------------------------
 Reporter:  sjmurdoch     |          Owner:  (none)
     Type:  defect        |         Status:  closed
 Priority:  Medium        |      Milestone:
Component:  Core Tor/Tor  |        Version:  Tor: 0.3.3.1-alpha
 Severity:  Normal        |     Resolution:  invalid
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------

Comment (by teor):

 The relevant cross-platform advice is:
 {{{
 If you write a server: listen on [::], [::1], 0.0.0.0 and 127.0.0.1 only.
 These pseudo-addresses are unconditionally available. If you always bind
 to these addresses you will have code that doesn't have to react to
 network changes, as all you listen on is catch-all and private addresses.
 }}}

 Tor already implements binding to 0.0.0.0 and dynamically determining the
 IPv4 address at runtime. This is the default behaviour when Tor is
 configured using ORPort or DirPort without an explicit address.

 Tor will be able to dynamically determine its IPv6 address when IPv6
 reachability checks (#6939) are implemented. This depends on IPv6 extends
 (#24403).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25182#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online