-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Thus "Tony Sarendal" <[EMAIL PROTECTED]> spake on Sat, 20 Oct 2007 18:16:21 +0100:
> On 10/20/07, Timo Schoeler <[EMAIL PROTECTED]> wrote: > > > > Hi list, > > > > on a customers' site I have a problem connecting from within their > > LAN (OpenBSD machine) crossing their router (Linksys BEFSX41, doing > > NAT) to a machine on the internet via SSH: Sessions die after some > > time due to 'timeouts'. > > > > If the connection is not used heavily (e.g. showing top(1)) it dies > > (the router clearing it's session cache); it's a well-known issue > > with this kind of customer-class devices (lots of entries on your > > favorite search engine). > > > > A solution (for GNU/Linux) would be to increase > > > > /proc/sys/net/ipv4/tcp_keepalive_time > > > > as I got from a newsgroup; however, on OpenBSD I just see > > > > net.inet.tcp.keepinittime > > net.inet.tcp.keepidle > > net.inet.tcp.keepintvl > > > > I tried to increase (and decrease, just to determine if there's any > > difference) net.inet.tcp.keepidle, but it didn't make a difference. > > Think I'm using the wrong knob -- is there something similar on > > OpenBSD (like tcp_keepalive_time) to cheat on the NAT thing? > > > > (And, yes, using a WRAP board running OpenBSD as router works > > perfectly well in the same environment; however, the Linksys has to > > stay there...) > > > > TIA, > > > > Timo > > > You can ask ssh to do keepalives for you. > Look at the ServerAliveInterval and ClientAliveInterval in ssh. > > /Tony Thanks! :) Timo iD8DBQFHGjySUY3eBSqOgOMRCmtlAJ420lPBP+YXuqoEdBdCD6nUja2RwgCeJUJ+ SpVAuNTY5Eq8JAAffMbwgvY= =+OzY -----END PGP SIGNATURE-----
