New answers tagged

0

You should be able to accomplish what you're looking to do with something similar to: ssh -i cloudkey -L 6000:localhost:6001 admin@54.152.188.55 -p 9000 -t "ssh -D 6001 -p 6666 localhost -l dancloud" the -t flag forces a pseudo-tty on the first machine and executes the remaining code on the first machine; in this case, ssh to the dancloud tunnel. The ...


1

First possibility is obvious (note the -t switch): ssh -t -i cloudkey -L 6000:localhost:6001 admin@54.152.188.55 -p 9000 \ "ssh -D 6001 -p 6666 localhost -l dancloud" With ProxyCommand it is more complicated on the first sight, but conceptually you need only one forwarding (netcat version is not advised anymore, using -W switch is more elegant): Host ...


2

I found the answer https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Proxies_and_Jump_Hosts SOCKS proxy via an Intermediate Host If you want to open a SOCKS proxy via an intermediate host, it is possible: $ ssh -L 8001:localhost:8002 user1@machine1.example.org -t ssh -D 8002 user2@machine2.example.org The client will see a SOCKS proxy on ...


2

You're on the right track with tty, and the -t option gives you just that. However, unless you are actually aiming to get a tty session for interacting, leave this option off of the last ssh command in your chain. In your case you just need it on the first connection: ssh -L 5901:localhost:6000 host1 -t ssh -L 6000:localhost:5901 -N host2 Now when you use ...


1

In summary, yes, ssh tunnels send all data across the port ssh is using (which is usually port 22). However, it only sends traffic specifically sent over the port you specify (5900 in your example above). The classic example of this is tunnelling web traffic, so that a local web browser uses the tunnel to reach destination web sites. In this instance, the ...


1

This line: tcp 0 1 10.0.85.14:52501 135.142.205.131:22 SYN_SENT 2366/ssh tells us, that the ssh-connection from the work pc to the home-pc has not been completed. So either a) the port forwarding from the router to the home-pc does not work, or b) the ssh-d on the home pc is not listening to the (correct) address


0

I found the -M option of autossh to be unreliable and always use -M 0 and let SSH do the connection monitoring, along with TCPKeepAlive=yes (resp. "no" for interactive connections) and ServerAliveInterval=30.



Top 50 recent answers are included