![]() There are passwords in plain text (in command line / PuTTY config) when -l user -pw password is used (doesn't matter if you use PuTTY placeholder %proxypass). Use -t (in both plinks) so that your terminal signals work (since you are not invoking a remote shell on the jump hosts) Plink -nc dIP:dPort -proxycmd "plink -loghost jHost1 -nc jIP2:jPort2" Your approach is correct, just use plink to jHost1 as a local proxy for the plink to jHost2: PuTTY -> jHost1 (jIP1) -> jHost2 (jIP2) -> Destination (dIP) ![]() If you are limited to Windows, Cygwin may have some more flexible SSH tools. It's not an ideal solution, but it may work if this is your only option.Įdit: If you're not limited to Windows/Putty, this (Transparent Multi-hop SSH) may do what you want. I've only ever done this with 2 hops so I don't know how it will perform. Open one more instance of Putty and connect to Localhost:2223 to access Machine4.connect to Localhost:2222) AND defines a new tunnel to forward an additional port (2223 for example) to Port 22 on Machine4 (your 3rd hop). Then open another Putty instance on your Windows Machine that uses the tunnel (i.e.Define a tunnel in Putty that forwards a port on your local machine (2222 for example) to Port 22 on Linux Machine2.If you are actually trying to get to a third network, you can open up another instance of Putty that connects via a tunnel defined on your original Putty instance. You can set up multiple tunnels to as many machines as you need to. If you're simply trying to get to another machine on the same 192.168.1.x network as Linux Machine 1/2, use an actual SSH Tunnel (found under Putty's Connection -> SSH -> Tunnels menu). It's not clear if you are just wanting to connect to an additional machine on the same network as Linux Machines 1/2 or if you need to jump to another network beyond them (for example Machine 4 on 172.22.1.x).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |