On Thu, 22 May 2003, Tony Godshall wrote: > For that to work the script I hook into inetd would have to > be smart enough to figure out where it is (home, office,
If autodetection doesn't work, you could always have a "clue" file ( eg "/etc/where" or similar ). > A downside with using inetd is that the ssh connections > take a few seconds to come up, and the one that does the > actual tunnelling (back to my laptop) sometimes doesn't come > up on the first attempt, so it's a bit of a delay, I'd think. True - it does take a while. I was thinking the main benefit would be not needing to write a watcher to restart it. > Another would be that it connects to a particular port, > right? Would I have to run an ssh command for each port I > want to forward then? I'd think there's less overhead in > making one ssh connection and running the multiple tunnels Probably, I suppose what you really want is the ability to make the running ssh tunnel add ports to forward on demand, but I don't think you can do that.
