Opened 5 years ago

Last modified 2 years ago

#15715 accepted defect

spurious "Network is unreachable" error after setting DisableNetwork=1

Reported by: mcs Owned by: arma
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.6.6
Severity: Normal Keywords: tor-client, bootstrap, sponsor8-maybe, disablenetwork, tbb-needs
Cc: brade, mikeperry Actual Points:
Parent ID: Points: small
Reviewer: Sponsor:

Description

If DisableNetwork is set to 1 via SETCONF during bootstrapping, Tor sometimes generates spurious errors such as "Network is unreachable". Kathy and I saw this while testing a fix for #11879. We realize this may be difficult to fix due to the internal architecture / concurrency inside Tor.

See #15713 for steps to reproduce (but note that an error does not occur every time). In the log that is attached to #15713 you can see an example:

Apr 17 10:28:10.000 [warn] Problem bootstrapping. Stuck at 25%: Loading networkstatus consensus. (Network is unreachable; NOROUTE; count 1; recommendation warn; host 847B1F850344D7876491A54892F904934E4EB85D at 86.59.21.38:443)

(the error happens right away if it happens at all – no delay).

This problem may cause some Tor Browser users to be a little confused; all they need to do is click "Open Settings" while Tor Browser was starting up and they will sometimes see an error alert.

Child Tickets

Change History (9)

comment:1 Changed 4 years ago by teor

Milestone: Tor: 0.2.???
Points: small

comment:2 Changed 4 years ago by arma

Severity: Normal
Status: newneeds_information

Tied to #15713

comment:3 Changed 4 years ago by arma

Keywords: TorCoreTeam201606 added
Owner: set to arma
Status: needs_informationaccepted

comment:4 Changed 3 years ago by teor

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

Milestone renamed

comment:5 Changed 3 years 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:6 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:7 Changed 3 years ago by nickm

Keywords: TorCoreTeam201606 removed

comment:8 Changed 2 years ago by nickm

Keywords: tor-client bootstrap sponsor8-maybe disablenetwork added

comment:9 Changed 2 years ago by gk

Keywords: tbb-needs added; tbb-wants removed

Let's just use tbb-needs and use priority there to indicate how urgent we'd like to have those tickets fixed.

Note: See TracTickets for help on using tickets.