Date: Sun, 2 Jun 2019 18:18:48 -0400 (EDT) From: doug <doug@fledge.watson.org> To: John Johnstone <jjohnstone.nospamfreebsd@tridentusa.com> Cc: freebsd-questions@freebsd.org Subject: Re: ssh timeout question Message-ID: <alpine.BSF.2.20.1906021800500.47760@fledge.watson.org> In-Reply-To: <d466ec6c-4aa1-52ed-3e52-c0678963d341@tridentusa.com> References: <alpine.BSF.2.00.1905271212240.61593@bucksport.safeport.com> <8daaed74-b18c-7b3d-12ff-baa76f894bfc@tridentusa.com> <3C8F1DFF-55B0-4A05-9B7B-B05B64676999@kreme.com> <d466ec6c-4aa1-52ed-3e52-c0678963d341@tridentusa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 31 May 2019, John Johnstone wrote: > On 5/28/19 3:00 PM, @lbutlr wrote: >> On 28 May 2019, at 05:37, John Johnstone >> <jjohnstone.nospamfreebsd@tridentusa.com> wrote: >>> I also now have a Verizon G1100. I still have my .ssh/config file with >>> ServerAliveInterval set to 30 and I'm able to maintain ssh sessions for >>> many hours as long as the laptop is not set to sleep. >> >> It's not a bad idea to at least test this, but I do not have ~/.ssh/config >> at all and my Mac maintains a ssh connection for weeks at a time. >> Basically, unless I reboot my FreeBSD server or reboot my Mac, the >> connection stays up. > > I put the ServerAliveInterval in place a long time ago and didn't test the > need for it after that. I removed it and yes, connections are staying up > without it. Packet monitoring shows TCP Keep-Alives are being sent every 2 > hours. It's hard to talk about this without naming names. With Verizon and a router model. For me no connection is timed out using model Fios-G1100 unless the connection is running pine. In this case the connect is timed out, usually within 3 hours. I have not tried all the remedies suggested here as the work demand >> irritant level. I will eventually do this and report back.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1906021800500.47760>