Date: Tue, 28 May 2019 21:35:56 +0200 (CEST) From: =?UTF-8?Q?Trond_Endrest=C3=B8l?= <trond.endrestol@ximalas.info> To: freebsd-questions@freebsd.org Subject: Re: ssh timeout question Message-ID: <alpine.BSF.2.21.9999.1905282126260.5734@enterprise.ximalas.info> In-Reply-To: <44imtu8k54.fsf@be-well.ilk.org> References: <alpine.BSF.2.00.1905281433400.27739@bucksport.safeport.com> <44imtu8k54.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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? 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 -- Trond.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.9999.1905282126260.5734>