(Advanced Users Pls) Plumbing for Tor
I am experimenting with Whonix, which is an OS specifically for Tor. It comes as two VirtualBox appliances, a Gateway (connextion to Tor), and a Workstation (working environment).
The Gateway NATs through the host to The Internets, connecting with Tor servers. First of all, this is a problem because my host firewall is very tight (Shorewall) and I am getting numerous violations. I don't know what ports it wants though, but it is alot, nor whether out -and- in.
The two VMs communicate through a dedicated vbox internal network. What I want to do is not just use this Tor connexion in the Workstation, but to extend it to my LAN for Tor Browser Bundle. So my first thought was to change this internal network to a host-only. This way the two VMs could still communicate, and an interface is created on the host so that the rest of the LAN could join the party. But how to share ports served on vboxnet0?
Don't worry about security at the moment; I'll be using TBB.
Well by default the internal network of Whonix between the Gateway and Workstation is set to 192.168.0.*. I couldn't allow this, because alot of routers have this as their default range, so I modified numerous config files in Gateway and Workstation to 192.168.2.*. Works now, and I have the vboxnet0 interface on the host as 192.168.2.3.
I ran an nmap scan on 192.168.2.3 though, and got only SSH and MythTV ports open. This looks like the external interface to the host (eth0), not vboxnet0. Why would this be?
The goal is to use the Gateway as a Tor server, for the whole LAN. It would serve ports 9050 & 9051 (whatever) to the host, and then the host would forward these through reverse SSH tunnels to remote machines. This would allow remote machines to use the Tor Browser Bundle Firefox to connect to Tor through the host & Gateway, and I could use TBB FF for everything, turning off Tor with the torbutton when I don't need it.
So, any config input?
Last edited by Quantumstate; 04-15-2013 at 06:36 PM.