Message-ID: <684c1bca@news.ausics.net> From: Computer Nerd Kev Subject: Re: How to get rid of client disconnected network sockets Newsgroups: comp.os.linux.networking References: <102ebko$2pkej$1@gwaiyur.mb-net.net> <102fi9j$2u1dt$5@dont-email.me> User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (Linux/2.4.31 (i686)) NNTP-Posting-Host: news.ausics.net Date: 13 Jun 2025 22:38:34 +1000 Organization: Ausics - https://newsgroups.ausics.net Lines: 19 X-Complaints: abuse@ausics.net Path: csiph.com!news.bbs.nz!news.ausics.net!not-for-mail Xref: csiph.com comp.os.linux.networking:8548 Lawrence D'Oliveiro wrote: > On Thu, 12 Jun 2025 12:54:16 +0200, Marcel Mueller wrote: >> The clients 192.168.121.24 is disconnected for at least an hour, but the >> sockets at the server seem to stay for an infinite time. > > This to me points to a defect in the protocol, that it does not > periodically exchange "are you there?" packets (even, say, once every 1 > minute or 5 minutes), just to be sure the other end is still up. But maybe the network connection was just interrupted and it'll be back in a few minutes? Since my home internet via mobile broadband is unreliable that often happens during SSH sessions. I can come back in 15min and my SSH terminals are all working again after the signal came back (well, not always, but sometimes). Mosh, which uses UDP, handles that better though. -- __ __ #_ < |\| |< _#