From: Crimson S. <cri...@gm...> - 2009-11-11 09:58:02
|
On Nov 11, 2009, at 10:51 , Tim Cutts wrote: > On 10 Nov 2009, at 1:31 pm, Crimson Scythe wrote: >> Personally, I only use the tunneling features. >> >> My home computer sadly sits behind an ISP-level NAT, which means I >> can't open any ports at all. To get around this, I use SSHKeychain to >> automatically launch tunnels with both forward and reverse port >> forwarding. The only major issue I've experienced in my use is if >> there's a network hick-up, or if my work computer goes down/reboots, >> causing the tunnels to go down. I'd _love_ to have SSHKeychain >> automatically detect stale/broken tunnels and relaunching them. In >> other words, some sort of persistent tunneling feature. Is this >> doable? > > Difficult to do in a reliable way, I'd have thought. How do you > tell the difference between a permanent failure (where you shouldn't > attempt to restart the tunnel) and a transient one, such as a > temporary network glitch while OSPF finds a new route through the > network? What time thresholds should you use before attempting to > restart the tunnel? Well, I guess setting a user-defineable time threshold could work? Let's say 5 minutes or so. If the tunnel is down for that long, can it even resume? As it is now, if the network has a glitch, I simply lose all contact with the computer until the tunnel is manually reestablished. --Thomas |