3 ms·
One that I frequently run into is that if you use SSH tunneling (like -L), you have to specify it the first time you ssh to that machine (i.e. when the ControlM
by georgebashi 13y ago
One that I frequently run into is that if you use SSH tunneling (like -L), you have to specify it the first time you ssh to that machine (i.e. when the ControlMaster is connected) and can't change it later. Using -L on later ssh's to the same machine silently fail, which can be infuriating if you don't realise it's happening. The best you can do at that point is to kill the ControlMaster ssh (disconnecting you across all your sessions), and then reconnecting with the right -L.
- croikle 13y agoYou can skip the master and spawn a fresh connection for your tunnel using `-o ControlPath=none`.
- croikle 13y agoIn fact, even better: you can add forwarding to your existing connection. <newline>~C opens a command line, which accepts the following commands: ssh> help Commands: -L[bind_address:]port:host:hostport Request local forward -R[bind_address:]port:host:hostport Request remote forward -D[bind_address:]port Request dynamic forward -KR[bind_address:]port Cancel remote forward (If you're not familiar with them, some of the other escape sequences are useful too. ~? lists them all.) [EDIT] Apparently, if you have a recent enough version, you can add a forward to the master with `ssh -O forward ...` [1] [1] http://serverfault.com/questions/237688/adding-port-forwardings-programmatically-on-a-controlmaster-ssh-session http://serverfault.com/questions/237688/adding-port-forwardi...