On Mar 20, 4:25pm, Christian Hamacher wrote:
> o (this is not exactly diald-related, but rather an ssh issue, but I
> would hope that other people on this list are using SSH ...)
> What I first tried to do is simply rely on the keepalive fea-
> ture of ssh to keep the link busy, and set a short timeout for
> SSH-initiated connections.
> However, it seems like diald is not reacting to any keepalive
> packets sent by ssh, or ssh is not sending any. I *do* have
> 'keepalive yes' in both the local ssh_config and the remote
> sshd_config. Is there anything special about SSH keepalive
> packets that make them invisible to diald in it's out-of-the
> box configuration?
Actually, I think you want to shut off keepalives for ssh since they
will detect when the connection goes down and terminate your ssh
session (which is not what you want). Here's the appropriate section
from the ssh man page:
KeepAlive
Specifies whether the system should send keepalive
messages to the other side. If they are sent,
death of the connection or crash of one of the
machines will be properly noticed. However, this
means that connections will die if the route is
down temporarily, and some people find it annoying.
The default is "yes" (to send keepalives), and the
client will notice if the network goes down or the
remote host dies. This is important in scripts,
and many users want it too.
To disable keepalives, the value should be set to
"no" in both the server and the client configura-
tion files.
In the past, when I've needed to keep tunnels alive for extended
periods of time, I would shut off the KeepAlive feature in ssh and
would simply have one side echo a short message to the other side
periodically. I'm not sure what you should do for interactive shell
sessions though.
Kevin
--
Kevin Buettner
[EMAIL PROTECTED], [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
