Skip to main content

Timeline for List open SSH tunnels

Current License: CC BY-SA 2.5

12 events
when toggle format what by license comment
Jul 10, 2015 at 17:48 review Suggested edits
Jul 10, 2015 at 18:14
Mar 2, 2011 at 9:49 comment added James Frost Yep, makes sense. Need to be a bit cleverer with the script then to parse the results, get a list of remote servers and execute the same command on each to retrieve the remote ports. Definitely doable. Will get on it!
Mar 2, 2011 at 9:47 vote accept James Frost
Feb 23, 2011 at 11:06 comment added akira for that you would have to either login to the server and execute the sshd-related lsof there (reliable) or parse the output of /proc/PID/cmdline for all of your ssh-commands .. which might give you misleading results since you can specify tunnels via .ssh/config as well.
Feb 23, 2011 at 10:33 comment added James Frost That's fine, its showing the remote IP address and the list of tunnelled ports. What I ideally want to know is what the remote port its tunnelled to. For example, if I've got a tunnel open from 3308 locally to 3306 on the server I want to see both.
Feb 21, 2011 at 13:31 history edited akira CC BY-SA 2.5
added 215 characters in body; added 4 characters in body
Feb 21, 2011 at 13:14 history edited akira CC BY-SA 2.5
added 262 characters in body
Feb 21, 2011 at 13:05 history edited akira CC BY-SA 2.5
deleted 6 characters in body
Feb 21, 2011 at 13:03 comment added akira thats the essence of a -L tunnel...
Feb 21, 2011 at 13:02 comment added shellholic The 3rd line is only there because the TCP socket is in use. It just says the something through a ssh tunnel has hit your local web server, not that the 33999 port is forwarded to the 80 one.
Feb 21, 2011 at 12:46 history edited akira CC BY-SA 2.5
added 605 characters in body
Feb 21, 2011 at 11:22 history answered akira CC BY-SA 2.5