Ssh – How to access a proxy enabled internet with ssh tunneling

connection-refusednetworkingPROXYsshssh-tunnel

I have two pc (A & B, Both are running ubuntu 16.04) that are connected through Local Network. PC-A has Internet connection. I want to browse internet in PC-B using ssh tunneling.

I used the command in PC-B –

ssh -D 9999 user@IP_ADDRESS

Then i set HTTP, HTTPS, FTP Proxy empty and SOCKS Proxy "localhost" and port 9999.

If PC-A has Internet connection which is not requires proxy setup , then i can browse network in PC-B using above command.

But if PC-A has Internet conenction which requires HTTP Proxy "xxx.yy.zz.zz" and port 8080 then i can't browse internet using the above command and terminal shows following error:

"channel 3: open failed: connect failed: Connection refused".

What should i do ? Any help is appreciated.

Best Answer

Have you considered running a proxy server, maybe squid, on PC-A? Then you can create a tunnel from PC-B on a given port to the input port on PC-A of the squid daemon.

Then you can configure squid to either use another upstream proxy (http://www.christianschenk.org/blog/using-a-parent-proxy-with-squid/) or directly connect to the internet depending on what you need.

Related Solutions

Ssh – setting up a proxy to mirror an SSH SOCKS connection

nylon supports SOCKS mirroring with ACL's

http://monkey.org/~marius/pages/?page=nylon

Ssh – How to automate SSH login with password

Don't use a password. Generate a passphrase-less SSH key and push it to your VM.

If you already have an SSH key, you can skip this step… Just hit Enter for the key and both passphrases:

$ ssh-keygen -t rsa -b 2048
Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/username/.ssh/id_rsa.
Your public key has been saved in /home/username/.ssh/id_rsa.pub.

Copy your keys to the target server:

$ ssh-copy-id id@server
id@server's password:

Now try logging into the machine, with ssh 'id@server', and check-in:

.ssh/authorized_keys

Note: If you don't have .ssh dir and authorized_keys file, you need to create it first

to make sure we haven’t added extra keys that you weren’t expecting.

Finally, check to log in…

$ ssh id@server

id@server:~$

You may also want to look into using ssh-agent if you want to try keeping your keys protected with a passphrase.

Best Answer

Related Solutions

Ssh – setting up a proxy to mirror an SSH SOCKS connection

Ssh – How to automate SSH login with password

Related Topic