On 2003-11-10 14:43:22 -0800, Mark Ferlatte wrote:
> Well, ClientAliveInterval exists in my version of ssh. :)
>
> ssh 1:3.4p1-1.woody.3
>
> I don't remember from your first message; are you running unstable?
testing with some packages from unstable. Concerning ssh:
Version: 1:3.6.1p2-9
--
V
Vincent Lefevre said on Tue, Nov 11, 2003 at 12:08:39AM +0100:
> On 2003-11-10 14:43:22 -0800, Mark Ferlatte wrote:
> > Well, ClientAliveInterval exists in my version of ssh. :)
> >
> > ssh 1:3.4p1-1.woody.3
> >
> > I don't remember from your first message; are you running unstable?
>
> testing
Vincent Lefevre said on Mon, Nov 10, 2003 at 10:48:21PM +0100:
> On 2003-11-10 13:24:28 -0800, Mark Ferlatte wrote:
> > Have you looking into ClientAliveInterval? ssh v2 has a built-in
> > keepalive mechanism that dodges some of the problems with regular
> > TCP keepalive, and you probably need to
On 2003-11-10 13:24:28 -0800, Mark Ferlatte wrote:
> Have you looking into ClientAliveInterval? ssh v2 has a built-in
> keepalive mechanism that dodges some of the problems with regular
> TCP keepalive, and you probably need to disable both of them to get
> what you want.
This option doesn't exist
Vincent Lefevre said on Mon, Nov 10, 2003 at 09:00:09PM +0100:
> This worked for several months, but since a few days, my ssh sessions
> get closed again (for the last one, I could see in the logs that it
> was closed during an ADSL reconnection). So, I did some tests with
> "ssh -v" and the follow
My ssh sessions from my local Debian machine were closed when there
was a route problem (or possibly after an ADSL reconnection), so I
added the following to my .ssh/config:
KeepAlive no
This worked for several months, but since a few days, my ssh sessions
get closed again (for the last one, I co
6 matches
Mail list logo