I'm trying to get internet to a Linux VM (Backtrack 5 on VMWare Workstation). Unfortunately I was told to not "bridge" the connection from the VM because it could be detected by our companies network admins.

Our company has a firewall and proxies for normal web browsing. I can get around it by ssh tunneling to a linux server (putty + ssh)

Is there a way I can get my Linux VM to have internet connection via SSH/Putty tunneling without it being detected on our corporate network? I'm not sure if I need to bridge my VM and change some settings on the Linux VM or if I need to alter VMWare somehow to grant internet to VMs via tunneling...?

Would appreciate any areas topics I should read into or any lead I can take to get accomplish this.

  • 2
    "circumvention of security or policy" is explicitly forbidden in the Serverfault FAQ. I wonder if it's accepted here. I have asked for clarification on meta. Jun 4, 2013 at 15:53
  • I'm not circumventing security or policy, we're working on a work around on this internally because it's holding our team back.. but till then we're pursuing alternatives
    – user772401
    Jun 4, 2013 at 16:54
  • 1
    Why do you care about the admins noticing it then? Jun 4, 2013 at 16:56
  • Because the admins noticing it means a box that they (the admins) have not protected (scanned, installed anti-v, etc) is on the network which would not be cool with them. An alternative soln is for us getting an external internet connection (which we're looking at).. but i'm thinking there must be a way to get internet to the VMs without making them active nodes on the network (my guess)
    – user772401
    Jun 4, 2013 at 17:26
  • @Mat Nonsense. Please keep it technical, don't prevent people from answering on-topic questions due to your mistaken sense of propriety. Jun 5, 2013 at 1:02

2 Answers 2


There are different ways to achieve this. When using a SOCKS5 proxy (SSH Tunnel) you actually still leak some information. SSH is a stateful protocol which uses TCP, however DNS requests use the UDP protocol (stateless) which can't be sent over the SSH tunnel. I did a blog post on this once which you can find here.

There are also other ways like tunneling over DNS (which is unreliable and extremely slow). However do note that circumventing policy can make you liable if your tunnel is responsible for breaching or introducing malicious programs/users into your corporate network environment. There is a reason why your admins wouldn't be cool with it.


While we wait for the clock to tick down on whether this is deleted, I will say this: If your client has an X11 display, you can do regular X11 forwarding over it. If not (probably not, since you're using Putty/Windows) you can try installing xming and configure PuTTY to X11 forward to your local XMing server.

Once you do that, you can run firefox or chrome on the remote machine. Just make sure you've enabled compression on the PuTTY and server side, otherwise there can be quite a bit of lag, especially over slower links.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.