[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #10405 [Tor]: Bug: Tried to open a socket with DisableNetwork set.
#10405: Bug: Tried to open a socket with DisableNetwork set.
------------------------+------------------------------------
Reporter: arma | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: 0.2.3.x-final
Component: Tor | Version:
Keywords: tor-client | Actual Points:
Parent ID: | Points:
------------------------+------------------------------------
{{{
$ src/or/tor bridge 128.31.0.34:9009 disablenetwork 1 usebridges 1
Dec 15 04:50:47.533 [notice] Tor v0.2.4.19 (git-e719d05fd296a9dd) running
on Linux with Libevent 2.0.19-stable and OpenSSL 1.0.1e.
[...]
Dec 15 04:50:47.539 [notice] DisableNetwork is set. Tor will not make or
accept
non-control network connections. Shutting down all existing connections.
[...]
Dec 15 04:50:48.697 [notice] Bootstrapped 5%: Connecting to directory
server.
Dec 15 04:50:48.698 [warn] connection_connect(): Bug: Tried to open a
socket with DisableNetwork set.
Dec 15 04:50:48.698 [warn] Problem bootstrapping. Stuck at 5%: Connecting
to directory server. (Network is unreachable; NOROUTE; count 1;
recommendation warn)
}}}
Noticed because I had a bridge configured in my tbb3.0rc1 but TBB had
failed to work on the last run, so it popped up the "connect or configure"
dialog box but then it popped up the "Tor failed to establish a Tor
network connection.\n\nNetwork is unreachable" error box right after.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10405>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs