Russ Allbery wrote: > Jeffrey Altman <[EMAIL PROTECTED]> writes: > >> I have found that with the Linksys routers that SSH sessions drop after >> 10 or 15 minutes of being idle if the server decides it wants to send >> data to the client. It may be that the NAT will allow the client to >> re-use the same external port if it sends data, but the mapping is >> certainly removed in the in-bound direction after a relatively short >> period of time. > > SSH has a keep-alive option to work around this that keeps pinging the TCP > session every few minutes. Maybe we could do something similar? It would > require a bit more load on the server since the client would have to ping > and the server respond to refresh the NAT timeout.
I am sure that you are aware that the clients already do implement a ping protocol with separate timeouts for UP and DOWN servers. It works when it works and it fails when it fails. The 1.4.1 file servers should be doing a good job of tracking mobile clients. If you are experiencing problems, please let us know. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
