Comments on: Tunnel Web and DNS Traffic Over SSH

By: Will Banks

Will Banks — Tue, 28 Sep 2010 11:36:05 +0000

I can’t seem to get firefox to save the change I made to network.proxy.socks_remote_dns with about:config.
What am I missing?

By: Radu

Radu — Sun, 06 Sep 2009 12:42:00 +0000

dns tunneling is available only for firefox – anyway to use it for ie for instance?

By: Afe

Afe — Sat, 03 Jan 2009 14:52:40 +0000

great tips! I like it.

By: max

max — Mon, 18 Aug 2008 22:42:11 +0000

I would suggest the modification of changing the setting to “-D 127.0.0.1:8080″ to make sure that only the local machine can have access to the tunnel/proxy.

This requires a somewhat new version of openssh (the version that came w/ redhat EL3 was too old).

By: blink4blog

blink4blog — Thu, 17 Jul 2008 15:23:36 +0000

Is there any complete tutorial that setup the whole infrastructure, I would like to use SSH connection thru my server at hosting centre wherever i goes.

Currently my server is SSH enable, do i
need to setup anything on the server side?

I assume the command mentioned above:

ssh -D 8080 -fN user@server

is client connection to server right? Do i have to run this everytime login into system or can it be set at system level so that wherever i connected will go through this setting?

Thanks

By: blue_lizard

blue_lizard — Wed, 18 Jun 2008 14:04:07 +0000

But what if your application is not SOCKS compliant?
Then you can use -w with ssh and set up an tunnel. Creating an virtual interface has a lot of benefits like transparent networking and routing.
Of course you need root access on both sides.

By: Stoffe

Stoffe — Wed, 18 Jun 2008 12:48:47 +0000

I use a SSH tunnel just like this, but I like to change the GNOME (Ubuntu) settings instead, and Firefox to use System settings. This way everything I use goes that way… It even seems Firefox in Hardy came with this turned on by default which of course is great for integration.

Especially important now, in Sweden…