[tbb-bugs] #16281 [Tor Browser]: Updating to 4.5.1 sets DisableNetwork

[Tor Bug Tracker & Wiki]

#16281: Updating to 4.5.1 sets DisableNetwork
-----------------------------+-----------------------
     Reporter:  saint        |      Owner:  tbb-team
         Type:  defect       |     Status:  new
     Priority:  minor        |  Milestone:
    Component:  Tor Browser  |    Version:
   Resolution:               |   Keywords:  meek, tbb
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-----------------------
Description changed by saint:

Old description:

> Not sure if this is intentional or not, so posting a report.  I'd had
> meek enabled before the update, and after the update couldn't get Tor
> Browser to connect to the internet.  The fix was to change TBB settings
> to no longer use a pluggable transport.
>
> Here's the log:
> {{{
> 06/03/2015 06:14:03.485 [NOTICE] DisableNetwork is set. Tor will not make
> or accept non-control network connections. Shutting down all existing
> connections.
> 06/03/2015 06:14:03.485 [NOTICE] Opening Socks listener on 127.0.0.1:9150
> 06/03/2015 06:14:16.441 [WARN] The communication stream of managed proxy
> './TorBrowser/Tor/PluggableTransports/meek-client-torbrowser' is
> 'closed'. Most probably the managed proxy stopped running. This might be
> a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please
> enable logging on your managed proxy and check the logs for errors.
> 06/03/2015 06:14:16.441 [NOTICE] Failed to terminate process with PID
> '14392' ('No child processes').
> 06/03/2015 06:14:17.242 [NOTICE] Closing no-longer-configured Socks
> listener on 127.0.0.1:9150
> 06/03/2015 06:14:17.242 [NOTICE] DisableNetwork is set. Tor will not make
> or accept non-control network connections. Shutting down all existing
> connections.
> 06/03/2015 06:14:17.242 [NOTICE] Closing old Socks listener on
> 127.0.0.1:9150
> }}}

New description:

 Not sure if this is intentional or not, so posting a report.  I'd had meek
 enabled before the update, and after the update couldn't get Tor Browser
 to connect to the internet.  The fix was to change TBB settings to no
 longer use a pluggable transport.

 Here's the log:
 {{{
 06/03/2015 06:14:03.485 [NOTICE] DisableNetwork is set. Tor will not make
 or accept non-control network connections. Shutting down all existing
 connections.
 06/03/2015 06:14:03.485 [NOTICE] Opening Socks listener on 127.0.0.1:9150
 06/03/2015 06:14:16.441 [WARN] The communication stream of managed proxy
 './TorBrowser/Tor/PluggableTransports/meek-client-torbrowser' is 'closed'.
 Most probably the managed proxy stopped running. This might be a bug of
 the managed proxy, a bug of Tor, or a misconfiguration. Please enable
 logging on your managed proxy and check the logs for errors.
 06/03/2015 06:14:16.441 [NOTICE] Failed to terminate process with PID
 '14392' ('No child processes').
 06/03/2015 06:14:17.242 [NOTICE] Closing no-longer-configured Socks
 listener on 127.0.0.1:9150
 06/03/2015 06:14:17.242 [NOTICE] DisableNetwork is set. Tor will not make
 or accept non-control network connections. Shutting down all existing
 connections.
 06/03/2015 06:14:17.242 [NOTICE] Closing old Socks listener on
 127.0.0.1:9150
 }}}

 Ubuntu 14.04 x64

--

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