Re: ssh ServerAlive probes

Christian Grunfeld <[email protected]> Wed, 6 Apr 2011 11:41:02 -0300
Newsgroups gmane.network.openssh.general
Message-ID <[email protected]>
Why cant you put a packet on the link up to the data transfer is
finish? What is your MTU ? that is what MTU is for. Or perhaps your
MTU into time units is bigger than you want to signal !

Cheers


2011/4/5 Don Tucker <[email protected]>:
> Hello,
>
> I am working on an application that needs to be able to rapidly detect a
> lost connection between an ssh client and ssh server. =A0I am using ssh t=
o do
> local and remote port forwarding, and sending data across the forwarded
> ports. =A0I was originally relying upon the TCPKeepAlive probes, but foun=
d
> that I could not consistently detect a lost detection. =A0Using the
> ServerAliveInterval and ServerAliveCountMax options, however, I am able t=
o
> consistently detect a lost connection. =A0The problem is, if I am using a
> low-bandwidth connection (cellular modem), and I am pushing a significant
> amount of data across, it seems that this hinders the communication betwe=
en
> the client and server with the ServerAlive messages. =A0In other words, w=
hen I
> am actually USING the connection, my application can mistakenly detect th=
e
> connection as lost because the ServerAliveInterval x ServerAliveCountMax =
is
> exceeded without a response from the server. =A0I was surprised at this
> behavior, since I expected the ServerAlive probes to only start after dat=
a
> flow between the client and server machines across that connection had
> ceased, but perhaps I am misunderstanding. =A0I do not have much leeway a=
s to
> how the server is configured. =A0Can someone recommend a way to be able t=
o
> both (1) quickly detect a lost connection [which, seems to require the
> interval and countmax be small], but not mistakenly detect the connection=
 as
> lost when it is being used?
>
> Thank you for any assistance.
>
> Don
>
>
>
>