Date: Tue, 08 Jul 2003 13:42:47 -0700 From: "Philip J. Koenig" <pjklist@ekahuna.com> To: Freebsd-questions@freebsd.org Subject: Re: ssh keepalives Message-ID: <20030708204248437.AAA218@empty1.ekahuna.com@dyn205.ekahuna.com> In-Reply-To: <20030708110837.Q54307@njamn8or.no-ip.org> References: <20030703071803206.AAA1059@empty1.ekahuna.com@dyn205.ekahuna.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8 Jul 2003 at 11:10, Viktor Lazlo boldly uttered: > On Thu, 3 Jul 2003, Philip J. Koenig wrote: > > > One of those firewalls is quite flexible about protocol state > > timeouts, I can set this on a service-by-service basis. (ie I could > > increase it for SSH and no other service) > > > > Unfortunately the firewall on the other side isn't so accommodating. > > It has a single timeout setting that affects all traffic that > > traverses the firewall, and I'd rather not increase that too high. > > If there is no option then run a low-bandwidth application in the > background to keep the connection alive, or script something to generate > some activity at frequent enough intervals to do so. Well that goes without saying, but the idea was whether the protocol itself contained a "keepalive" function. It's still a pain to have to go through that just so a connection will not die after 5 mins. I would think this is a common enough issue to justify an enhancement request to the open-ssh people. -- Philip J. Koenig pjklist@ekahuna.com Electric Kahuna Systems -- Computers & Communications for the New Millenium
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030708204248437.AAA218>