On Tue, Dec 11, 2007, Amos Shapira wrote about "Re: ssh timout": > On 11/12/2007, Biran, Yahav (Yahav) <[EMAIL PROTECTED]> wrote: > > Hi all, > > when ever I connect to a linux server using ssh, the connection is timeout > > after less then a 3 min without interacting with the server. > > I used to get this too until I set "ServerAliveInterval" to "120" in > my .ssh/config.
Thanks for the very helpful tip!! In recent years, in fewer and fewer cases do I get a "straight", end-to-end TCP connection. More and more "firewalls", "load balancers" and other crap mess with my connections. Unfortunately one of the things these devices take the liberty to do is to disconnect "inactive" connections (where inactive might mean just a few minutes). Why do they take this liberty? What RFC says they can? Who knows... I was actually looking for exactly this parameter in Ssh, but haven't noticed it before. I guess last time I looked was before Ssh 2 (when this parameter was introduced). I just checked it, and it worked like a charm. Finally I can leave an Ssh connection for hours - like I always used to do before the proliferation of firewalls and similar devices. By the way, I think that on today's Internet, something like "ServerAliveInterface 120" should be made the default... -- Nadav Har'El | Wednesday, Dec 12 2007, 3 Tevet 5768 [EMAIL PROTECTED] |----------------------------------------- Phone +972-523-790466, ICQ 13349191 |You do not need a parachute to skydive. http://nadav.harel.org.il |You only need one to skydive twice. ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
