{"id":868,"date":"2008-12-11T02:26:21","date_gmt":"2008-12-10T20:26:21","guid":{"rendered":"http:\/\/www.dotcomunderground.com\/blogs\/?p=868"},"modified":"2020-12-21T20:54:18","modified_gmt":"2020-12-21T14:54:18","slug":"putty-ssh-tunnel-to-hide-ip","status":"publish","type":"post","link":"https:\/\/www.dotcomunderground.com\/blogs\/2008\/12\/11\/putty-ssh-tunnel-to-hide-ip\/","title":{"rendered":"Using SSH Tunnel with PuTTY to browse internet hiding your IP address"},"content":{"rendered":"

If you have access to SSH on a remote server (dedicated server, vps or shell account), you can browse the internet over the IP address hiding your original IP address.<\/p>\n

This can be useful for many scenarios like –<\/p>\n

IP based authentication over dynamic IP<\/strong>:
\nIn many cases for security reasons we use restrict access only to some selected IP addresses. For example, admin area of a blog, forum, billing system or help desk can be protected with IP based authentication.
\nBut what if you are on dynamic IP? You can allow your users (or yourself) first to ssh to a server with static ip and then access your restricted web app over the ssh tunnel. Your restricted web app will get the remote server IP as the user IP.<\/p>\n

Technical limitations related to shared\/dynamic IP<\/strong>:
\nIn many places (specially in Bangladesh) ISPs provide the clients only with dynamic or shared IP address. In some places access are limited by number of access per IP address.
\nFor example, download services like RapidShare will not allow you to download a file when someone else is downloading a file over your shared IP. You can easily bypass such limits using this SSH Tunneling.
\nJust last night I had to use ssh tunneling to create a couple of Live IDs (passport.net) as Micro$oft was not allowing to create any from my local ISP IP :S<\/p>\n

Being a cool geek<\/strong>:
\nOr you can use it just to surprise your friends (who actaully checks for your ip =P) by showing your domain on you email and forum posts ;)<\/p>\n

Anyways… enough of possible “usage”. If you are reading this, I bet you already “need it” =P<\/p>\n

Now to get straight into the tutorial.<\/p>\n

What you need?
\n1. PuTTY SSH Client. (Can be downloaded from here<\/a>.)
\n2. Firefox Web Browser. (Can be downloaded from here<\/a>.)
\n3. SSH access to a unix\/linux server. (Now thats something I can’t give you ;) )<\/p>\n

Now, first run PuTTY. You should be on the “PuTTY Configuration<\/strong>” window. On the “Host Name (or IP address)<\/strong>” field, type the hostname or IP address of your remote server. And select “Connection type<\/strong>” as “SSH<\/strong>“. The port should get automatically selected to 22.
\n\"PuTTY<\/p>\n

Then, in the left-hand menu, click on “SSH<\/strong>“. In “Protocol options<\/strong>“, tick “enable compression<\/strong>” and set your preferred SSH version to “2<\/strong>“.
\n\"PuTTY<\/p>\n

Now expand the “SSH<\/strong>” menu and select the “Tunnels<\/strong>” sub-menu.
\n\"PuTTY<\/p>\n

Now under the “Tunnels<\/strong>” menu (Options controlling SSH port forwarding), in the “Source port” field, type in a source port. Here I am using 4567<\/strong>. But you can use anything. Then select “Dynami<\/strong>c” as “Destination<\/strong>” and click the “Add<\/strong>” button.
\n\"PuTTY<\/p>\n

After clicking the “Add” button the newly added forwarded port should get listed under “Forwarded ports<\/strong>” list.
\n\"PuTTY<\/p>\n

Now, go back to the “Session<\/strong>” tab at the top of the menu, give the new connection a name (here i used My SSH Proxy) and click on the “Save<\/strong>” button.
\n\"PuTTY<\/p>\n

Congrats! we are done with the PuTTY configuration.<\/p>\n

From now on you can use this connection to login to your server. After login, you winn be able to use the connection as SSH Tunnel.<\/p>\n

But before starting to browse internet using the IP address of the server, we need to configure firefox settings.<\/p>\n

Lets fire up the fox and go to “Tools > Options…<\/strong>”
\n\"Firefox<\/p>\n

Now click the Advanced<\/strong> icon (on the upper-right of the dialog), and select the Network<\/strong> tab. Then click on the “Settings…<\/strong>” button.
\n\"Firefox<\/p>\n

This will brings up the “Connection Settings<\/strong>” dialog. On this dialog click the “Manual proxy configuration<\/strong>” radio button, then put the address 127.0.0.1<\/strong> in the “SOCKS Host<\/strong>” field. In the “Port<\/strong>” field enter the port you used when configuring your SSH tunnel with Putty. In my case this port is 4567<\/strong>.
\n\"Firefox<\/p>\n

Click the “OK<\/strong>” buttons to accept your changes.<\/p>\n

Done!<\/p>\n

Now make sure you have already logged in to the server using the connection we created with PuTTY and start browsing with Firefox.<\/p>\n

You can visit a IP address identifier site like WhatIsYourIp.com<\/a> or Whois.com.bd<\/a> to check which IP address firefox is showing.<\/p>\n

If you do not already have access to a linux server or shell account, you can grab a high performance vps<\/a> from evolution-host.com<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

If you have access to SSH on a remote server (dedicated server, vps or shell account), you can browse the internet over the IP address hiding your original IP address. This can be useful for many scenarios like – IP based authentication over dynamic IP: In many cases for security reasons we use restrict access […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,9,13],"tags":[182,126,179,181,180,127],"class_list":["post-868","post","type-post","status-publish","format-standard","hentry","category-tech","category-tips","category-tutorials","tag-firefox","tag-linux","tag-proxy","tag-putty","tag-socks-proxy","tag-unix"],"_links":{"self":[{"href":"https:\/\/www.dotcomunderground.com\/blogs\/wp-json\/wp\/v2\/posts\/868","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dotcomunderground.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dotcomunderground.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dotcomunderground.com\/blogs\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dotcomunderground.com\/blogs\/wp-json\/wp\/v2\/comments?post=868"}],"version-history":[{"count":0,"href":"https:\/\/www.dotcomunderground.com\/blogs\/wp-json\/wp\/v2\/posts\/868\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dotcomunderground.com\/blogs\/wp-json\/wp\/v2\/media?parent=868"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dotcomunderground.com\/blogs\/wp-json\/wp\/v2\/categories?post=868"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dotcomunderground.com\/blogs\/wp-json\/wp\/v2\/tags?post=868"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}