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
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 w
On 3/1/23 05:03, Mike Karels wrote:
On 1 Mar 2023, at 5:36, Michael Gmelin wrote:
On 1. Mar 2023, at 11:35, Yuri wrote:
Windows system connects to FreeBSD through ssh and then this connection dies
because of WiFi or VPN issues.
FreeBSD still has the sshd process alive for this connection
On 1 Mar 2023, at 5:36, Michael Gmelin wrote:
>> On 1. Mar 2023, at 11:35, Yuri wrote:
>>
>> Windows system connects to FreeBSD through ssh and then this connection
>> dies because of WiFi or VPN issues.
>>
>> FreeBSD still has the sshd process alive for this connection for 30+ minutes.
>>
>> T
> On 1. Mar 2023, at 11:35, Yuri wrote:
>
> Windows system connects to FreeBSD through ssh and then this connection dies
> because of WiFi or VPN issues.
>
> FreeBSD still has the sshd process alive for this connection for 30+ minutes.
>
> TCP keepalive is enabled on the FreeBSD host:
>
>
Windows system connects to FreeBSD through ssh and then this connection
dies because of WiFi or VPN issues.
FreeBSD still has the sshd process alive for this connection for 30+
minutes.
TCP keepalive is enabled on the FreeBSD host:
$ sysctl net.inet.tcp.always_keepalive
net.inet.tcp.always_k
