Date: Sun, 9 Jun 2019 11:58:26 +1000 From: Anders Jensen-Waud <anders@jensenwaud.com> To: freebsd-questions@freebsd.org Subject: Re: ssh timeout question Message-ID: <4e4dfb73-fcf8-3255-d36f-a08c29d04287@jensenwaud.com> 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 29/5/19 5:35 am, 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? > > 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 I can second this. It works really nicely, especially when working on a mobile connection / on the go.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e4dfb73-fcf8-3255-d36f-a08c29d04287>