[tor-bugs] #25042 [Archived/Torouter]: Connecting to tor cuts my connection to the internet.

[Tor Bug Tracker & Wiki]

#25042: Connecting to tor cuts my connection to the internet.
-------------------------------+------------------------------------
 Reporter:  GGNderbomb         |          Owner:  ioerror
     Type:  defect             |         Status:  new
 Priority:  Medium             |      Milestone:  Tor: 0.3.1.x-final
Component:  Archived/Torouter  |        Version:  Tor: 0.3.1.8
 Severity:  Blocker            |     Resolution:
 Keywords:                     |  Actual Points:
Parent ID:                     |         Points:
 Reviewer:                     |        Sponsor:
-------------------------------+------------------------------------

Comment (by cypherpunks):

 I am not familiar with anonabox, but I'll give it a go.
 [[br]]
 > Advanced Configuration
 >> Virtual'''Addr'''Network 10.192.0.0/10
 >> Trans'''Port''' 9040
 >> TransListen'''Address''' 192.168.19.84
 >> DNS'''Port''' 9053
 >> DNSListen'''Address''' 192.168.19.84
 >> ClientTransportPlugin obfs2,obfs3,scramblesuit exec
 /usr/bin/'''obfsclient'''
 >> [...]
 >> ## Last updated 12 September '''2012''' for Tor 0.2.4.3-alpha
 >> ## (may or '''may not work for''' much older or '''much newer'''
 versions of Tor.)
 >> [...]
 >> ## Tor opens a socks proxy on port 9050 by default -- even if you
 >> ## configure one below. '''Set "SocksPort 0" if you plan to run Tor
 only'''
 >> ## '''as a relay, and not make any local application connections
 yourself.'''
 >> SocksPort 0

 I bolded some parts. Are the IPs beginning with 192. or the 10. with CIDR
 subnet and their ports the same as those that your devices are configured
 to connect through? Is SocksPort supposed to be 0 on anonabox, implying
 every device runs tor and thinks anonabox is a bridge? I don't see a
 [https://www.torproject.org/docs/bridges#RunningABridge BridgeRelay] line
 while SocksPort is 0. Does it not exist, or did you forget to attach a
 picture of it? Version 0.2.4.3 is extremely old, so you should start with
 a [https://gitweb.torproject.org/tor.git/tree/src/config/torrc.sample.in
 default torrc] for version 0.3.1.8 as a template and overwrite any line
 with the same variable as in yours with the value that yours is set to.
 New variables may have been introduced, deprecated, or removed altogether.
 Take the time to read the comments in the config file (lines starting with
 ##). Variables in the configuration file may be turned off or set to
 default by commenting-out their line (starting a line with a single # to
 make tor think it is a comment and ignore it).

 I cannot find the variables ''above'' the first comment line...
 > ## Configuration file for a typical Tor user
 ...in any versions of tor's torrc config file as far back as
 0.2.4.3-alpha, so those variables are probably used by anonabox and not by
 the tor binary executable. Copy those to your new configuration. While
 you're at it, look at the ClientTransportPlugin line. The Tor Project has
 deprecated obfsclient in favor of separate "pluggable transports" for
 bridge protocols. Check that obfsclient is updated or that obfs4proxy is
 installed and updated, and then consider changing...
 > ClientTransportPlugin '''obfs2,obfs3,scramblesuit''' exec
 /usr/bin/'''obfsclient'''
 to
 > ClientTransportPlugin '''obfs4,obfs3''' exec /usr/bin/'''obfs4proxy'''
 But be careful because other things in anonabox may not be designed for
 new versions of obfs4proxy.

 If you get it to work, send your procedure and a link to this ticket in a
 [https://www.chiark.greenend.org.uk/~sgtatham/bugs.html bug report] to the
 anonabox developers.

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