Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
Newsgroups: comp.os.linux.networking
Subject: Re: How to get rid of client disconnected network sockets
Date: Wed, 18 Jun 2025 05:30:09 -0000 (UTC)
Organization: the-candyden-of-code
Lines: 33
Message-ID: <slrn1054jfk.3ce8.candycanearter07@candydeb.host.invalid>
References: <102ebko$2pkej$1@gwaiyur.mb-net.net> <102fi9j$2u1dt$5@dont-email.me> <684c1bca@news.ausics.net> <102jgvr$3bor9$1@gwaiyur.mb-net.net>
Injection-Date: Wed, 18 Jun 2025 07:30:09 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="6c4f9373326aed7e8d4055fc0f36ba68"; logging-data="3102467"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18AiD9KBIWRLNcximyfOZ+yPcskVnYQJ0f5/wpED+FE3g=="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:k0oiVT43RAJdXcuswOzE0BG8Fk4=
X-Face: b{dPmN&%4|lEo,wUO\"KLEOu5N_br(N2Yuc5/qcR5i>9-!^e\.Tw9?/m0}/~:UOM:Zf]% b+ V4R8q|QiU/R8\|G\WpC`-s?=)\fbtNc&=/a3a)r7xbRI]Vl)r<%PTriJ3pGpl_/B6!8pe\btzx `~R! r3.0#lHRE+^Gro0[cjsban'vZ#j7,?I/tHk{s=TFJ:H?~=]`O*~3ZX`qik`b:.gVIc-[$t/e ZrQsWJ >|l^I_[pbsIqwoz.WGA]<D
Xref: csiph.com comp.os.linux.networking:8553

Marcel Mueller <news.5.maazl@spamgourmet.org> wrote at 09:56 this Saturday (GMT):
> Am 13.06.25 um 14:38 schrieb Computer Nerd Kev:
>> Lawrence D'Oliveiro <ldo@nz.invalid> 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).
>
> For this purpose I would recommend "screen". It keeps your ssh session 
> as long as you like.

Or tmux.

>> Mosh, which
>> uses UDP, handles that better though.
>
> UDP sadly fails if a NAT router is in between. Since it cannot know when 
> the connection is closed it just discards the port after a timeout w/o 
> traffic, typically only a few minutes.


Is there any way to change the timeout period?
-- 
user <candycane> is generated from /dev/urandom