1

ssh: which side is running the SOCKS proxy?

view story
linux-howto

http://serverfault.com – When I set up a tunnel using dynamic forwarding (ssh -D), which side is running the SOCKS proxy? That is, is the proxy running on the local end (client) or the remote end (server)? Here's the situation: I want to set up several tunnels chained together using -L. Should the -D tunnel be the last one in the chain or the first one? Edit: I found the answer to the second paragraph on Super User (the -D tunnel should be at the remotest end). But I'd still like to know where the proxy code is running. (HowTos)

grtyyu's picture
Submitted by grtyyu on 04/08/2012

Stories similar to ssh: which side is running the SOCKS proxy?

SSH Tunnel Questions 3 years 31 weeks ago

Basically, I am wanting to use my home linux server as a ssh tunnel / proxy. So that I can access services from the server.

I want to be able to use samba port 193 from another machine Cups would also be an added bonus later on down the road.

I have already configured firefox to work on a windows machine on a seperate network using this ssh forwarding.

Socks proxy: no, unless you can run ssh server or socks / http proxy on your windows machine.You can connect from your windows pc to your home pc using putty or plink with reverse tunnel (-R linux-machine-port:web-server-address:web-server-port) and then you should be able to connect to web-server using localhost:linux-machine-port.If you need dynamic proxy on windows side you can use other softwa

I have an apache virtual host running a reverse proxy accepting connections from the servers IP. To access, I'm running an SSH tunnel from localhost -> server, and pointing my browsers proxy settings at localhost:ssh-tunnel-port.

Occasionally (I don't have benchmarks) everything running through the proxy connection is slow.

I have successfully setup a tunnel over SSH on linux mint, and can browse the web.

However, when I try to ssh using the same port, I get:

Couldn't establish connection to proxy: Network is unreachable ssh_exchange_identification: Connection closed by remote host

In my mate-network-properties I have selected manual proxy configuration, and socks host is 127.0.0.1

So why doesn't ssh use th

I got a great answer for my previous question about connecting from Machine A to Machine C via Socks proxy located on Machine B.

Say Machine B Ip is 218.62.97.105 and it is listening on port 1080

The command for that:

ssh -o ProxyCommand='socat - socks:218.62.97.105:HOST_C:21,socksport=1080'

I wonder if it is possible to make a chain from the socks proxies.

Consider scenario: Machine A ->

Currently I create a ssh tunnel using: ssh user@server -D 1234 to use SOCKS proxy. How do I configure server so I can directly connect to socks server?

I want to set firefox socks host to server ip and port, instead of 127.0.0.1 and the port specified with -D parameter.

I have a list of SOCKS proxy servers from this site.

I've read about creating a dynamic tunnels with ssh -D and to be honest i've tried that already.

The man page to yum.conf describes several proxy related variables:

proxy URL to the proxy server that yum should use. proxy_username username to use for proxy proxy_password password for this proxy

But how to specify a SOCKS proxy?

I assume that the above is just for normal HTTP proxies ...

I am using Rasbian on my newly arrived Rasp.Pi, and decided to make it my own proxy server. Now I need to set up a ssh tunnel on the Pi to my Linode server, and make it auto start with the system.

What did I do:

Add this line to /etc/rc.local

autossh -f theRemoteServer -N -D 5555 -L 1234:localhost:22

After I reboot, I found out that I can't use the localhost:5555 as a socks proxy.