Date: Tue, 28 May 2019 14:42:22 -0400 (EDT) From: Doug Denault <doug@safeport.com> To: freebsd-questions@freebsd.org Subject: Re: ssh timeout question Message-ID: <alpine.BSF.2.00.1905281433400.27739@bucksport.safeport.com>
next in thread | raw e-mail | index | archive | help
On Tue, 28 May 2019, RW via freebsd-questions wrote: > On Tue, 28 May 2019 07:37:36 -0400 > John Johnstone wrote: > > >> It's very common for HTTP connections between web browsers and >> servers to also go idle before they are explicitly closed. This >> results in the states being removed prematurely by the router. This >> isn't noticed by the user though since the browser just opens a new >> connection to the server. >> >> My guess would be that DHCP or number of active connections are not a >> factor in your case. > > I doubt it's to do with timing out an idle connection since pine is > polling for new mail ever 150s. Thank you all for comments and suggestions. It would not have occurred to me to set the keep-alive value that small, I will try that. That is a lot less irritating than my print a char script that mucks up emails. In google I found someone suggesting setting "IPQoS throughput" in $HOME/.ssh/config. I am going to try both when I next go to a 100% fail location. I'll report back. I also find it strange that sitting in pine triggers the timeout but sitting idle for days does not. Doug _____ Douglas Denault http://www.safeport.com doug@safeport.com Voice: 301-217-9220 Fax: 301-217-9277
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1905281433400.27739>