Date: Wed, 29 May 2019 16:48:27 -0400 (EDT) From: doug <doug@fledge.watson.org> To: =?ISO-8859-15?Q?Trond_Endrest=F8l?= <trond.endrestol@ximalas.info> Cc: freebsd-questions@freebsd.org Subject: Re: ssh timeout question Message-ID: <alpine.BSF.2.20.1905291627480.31510@fledge.watson.org> In-Reply-To: <alpine.BSF.2.21.9999.1905282126260.5734@enterprise.ximalas.info> References: <alpine.BSF.2.00.1905281433400.27739@bucksport.safeport.com> <44imtu8k54.fsf@be-well.ilk.org> <alpine.BSF.2.21.9999.1905282126260.5734@enterprise.ximalas.info>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 28 May 2019, Trond Endrest?l wrote: > On Tue, 28 May 2019 15:16-0400, Lowell Gilbert wrote: > >> I don't run into issues with this because my remote sessions tend to >> have an application running that updates an on-screen time display every >> minute. That's not why I do it, of course. > > Unless you need X11 and/or port forwarding, why not try net/mosh? That is kind of the point, I use pine with a mouse. I was hoping someone might have any idea as to why running pine makes the session more likely to be timed out. Seems counterintuitive. When I first wrote my keep-alive script (over DSL) I did find that sending a <bell> or some other non-printing char did not stop timeouts. > mosh uses ssh to bootstrap itself before it switches to a UDP based > protocol running on a port > 60000. mosh is fairly resistant to packet > loss and allows for seamless roaming. Roaming is limited to IPv4 or > IPv6, depending on which protocol you chose when you did the initial > connect. The use of screen or tmux is highly recommended. More > information here: https://mosh.org We were thinking about using mosh with blink on IOS and kind of forgot. Thanks for the info. Doug
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1905291627480.31510>