On 9 Jul 2003 at 20:24, Paulius Bulotas boldly uttered: 

> Hi,
> a bit late answer, but I'm not able to keep up with my email traffic ;)
> Apply this patch to OpenSSH, if you are running FreeBSD:
> http://www.sc.isc.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html
> and use Heartbeat option with something less then dynamic rules life ;)
> Regards,
> Paulius

Aha, now this is a very interesting response!

Considering that the author of the patch greatly discourages usage of 
the older OpenSSH code, and considering that my recently updated 4.8-
STABLE box is still using OpenSSH 3.5p1 rather than the latest 3.6p1 
mentioned in the patch, I'm a little disinclined to do this patch 
because I'll have to re-patch it every time I build/install world.

If there's any possibility this patch will make it into the 
mainstream distribution I'll just wait for that.  Will wait and see, 
but thanks very much for the tip!

> On 03 07 01, Philip J. Koenig wrote:
> > 
> > I'm having a problem with premature termination of ssh sessions after 
> > an idle period of a few minutes, getting a "connection reset by peer" 
> > message.  I presume this is due to intermediate stateful firewalls 
> > closing the connection when no traffic passes for a period of time.
> > 
> > In the past I've addressed this issue when I have control of the 
> > destination host, by including the following parameters in 
> > sshd_config:
> > 
> > ClientAliveInterval 30
> > ClientAliveCountMax 4
> > 
> > 
> > However in this case I don't have control over the destination.  It's 
> > a self-contained network device.
> > 
> > man 5 ssh_conf says that "KeepAlive" is the default with ssh.  Is 
> > there any other tactic I can use to keep these connections from 
> > closing after a few minutes of inactivity?
> > 
> > Currently on FreeBSD 4.8-stable with OpenSSH_3.5p1

Philip J. Koenig                                       
Electric Kahuna Systems -- Computers & Communications for 
the New Millenium

[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to