Anti-idle in OpenSSH client?

[mandar at webchat.chatsystems.com]

KeepAlive doesn't do the trick  unfortunately - it merely sets
SO_KEEPALIVE on the socket, and is also not configurable. It's
actually meant as a way for ssh to know when the underlying
network connection to the remote server has gone away, when set.

I haven't yet been able to find the debian null packet patch
that was previously reported on this list...I found some mention at:

http://lists.debian.org/debian-user/2002/debian-user-200207/msg00255.html


but haven't been able to track down this patch...any plans to
include this in the official OpenSSH client release?

If someone has a copy, an email or URL would be greatly appreciated ;)

- Mandar

On Fri, 4 Apr 2003, Frank Cusack wrote:

> Date: Fri, 4 Apr 2003 16:06:16 -0800
> From: Frank Cusack <fcusack at fcusack.com>
> To: mandar at webchat.chatsystems.com
> Cc: openssh-unix-dev at mindrot.org
> Subject: Re: Anti-idle in OpenSSH client?
>
> On Fri, Apr 04, 2003 at 09:39:32AM -0600, mandar at webchat.chatsystems.com wrote:
> >    Most of the windows ssh clients (putty, securecrt) have anti-idle
> > features. They offer either a null packet or protocol no-op or user
> > defined string to be sent over every x seconds.
> >
> >    Is this possible or planned with the OpenSSH client? Our draconian
> > firewall admins have started timing out ssh sessions. Yes I'm aware I
> > could hack up a port forwarding dumb traffic process, but was looking for
> > a more elegant solution like the windows clients have. e.g. a command line
> > option to ssh that lets you anti-idle..
>
> See ssh_config(5), look for KeepAlive.
>
> /fc
>
> _______________________________________________
> openssh-unix-dev mailing list
> openssh-unix-dev at mindrot.org
> http://www.mindrot.org/mailman/listinfo/openssh-unix-dev
>