Date: Mon, 6 Mar 2023 17:44:54 -0800 From: Peter Wemm <peter@wemm.org> To: Mark Delany <n6t@oscar.emu.st>, freebsd-net@freebsd.org Subject: Re: sshd doesn't disconnect for 30+ minutes after the TCP connection is closed ungracefully Message-ID: <daa70592-e016-6d9d-e444-638e3a1d19c6@wemm.org> In-Reply-To: <0.2.0-final-1678136677.164-0xb079cd@qmda.emu.st> References: <baf5faa3-3c03-fb9e-4196-bd26c2fc622e@tsoft.com> <08DDB90C-5D30-40A3-86C0-87021959F04D@freebsd.org> <49CE5046-7934-414C-9B62-F3712DECBA52@karels.net> <540652d7-953b-12bc-42cc-982d4dd85849@wemm.org> <0.2.0-final-1678136677.164-0xb079cd@qmda.emu.st>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/6/23 13:04, Mark Delany wrote: > On 06Mar23, Peter Wemm allegedly wrote: >> (~/.ssh/config with ServerAlive* probes) for different reasons. The >> (overloaded) router would drop connections that seemed idle. Sending >> probes helped prevent that - or at least making the router drop somebody >> else's instead. > Probably explains why I, quite likely on the same shuttle, ended up running this on the > client side of my terminal sessions: > > while : > do > ssh snake.corp.youknowhoo.com tmux emacs > echo Some dirty rat caused my connection to drop...again! > sleep 2 > done > "mosh" turned out to be a better solution in the longer run for me. It would survive switching between shuttle and mobile data transparently. You needed a reliable jump host with udp access though. -Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?daa70592-e016-6d9d-e444-638e3a1d19c6>