DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 52SIgWdv437042
Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 52SIgWdv437042
Authentication-Results: delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=doMrR6y6
X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C5E033830618
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1743187351;
	bh=iZtt/QxmP+Qw1wTYPxb4ldqNJAl1k6zjKUY2uKann5I=;
	h=To:Subject:Date:List-Id:List-Unsubscribe:List-Archive:List-Post:
	 List-Help:List-Subscribe:From:Reply-To:From;
	b=doMrR6y6g4BqMtAGK2EKlqYZxP8N5n4xI+IhYFGDz5Fjnb5u0eAzQk/mTg6Ddyvci
	 hxKlVCRTIy8SFmTbKoAFFJVWjhAaQN7MHvPqtw9qkzy88nXxAqIBeZMnaoNQ3HL6Og
	 N6YQqiqGdJyKBY7n3dwbJlj0eb2FBVyEl/ner0Ic=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org DF9353857BA5
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org DF9353857BA5
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1743187326; cv=none;
 b=DpQ/cKRseD1YNiaKEjQuTA194HPhgpFIkGcsAOS2liZGHHtzGsIUaTqM+YPzsR1BIW+iTfR+2c+KcfU40gRg3dat0rsEYIswJBQP9cnllnBt2QCus2d3Dbw4KknH+gg75aeZvKvmyRHE1KXOKrWstaN68G25PjXGckT+NbVnbFs=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
 t=1743187326; c=relaxed/simple;
 bh=X7fANEojM6WJVRIwc4UKPl6JnzaG5vJBvJhJARAG+Ds=;
 h=DKIM-Signature:From:To:Subject:Message-ID:Date:MIME-Version;
 b=hNA0a/fBm0FerBk+yPQ/J1On75D/eXRBGjLBA3O+fe/ZH7bTJ/uwpsLsTeFJL/rplmGVn2/m3RcNptxvdm3UC7nlixPbgDLc2xjswjKiGDhUUxuatVli8TSN0zBi5M4AeGY28Rvb+6fq7+nFbkcqWs7KtvwzqIV/nymD/99u8zE=
ARC-Authentication-Results: i=1; server2.sourceware.org
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DF9353857BA5
X-Originating-Ip: 100.34.209.19
To: Soren <somian08 AT gmail DOT com>, cygwin AT cygwin DOT com
Subject: Re: sshd times out and disconnects client
Message-ID: <eb4f5785-f6ae-ad0b-0ebf-25faaae64c61@mindspring.com>
Date: Fri, 28 Mar 2025 18:42:02 +0000
MIME-Version: 1.0
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: "C. Linus Hicks via Cygwin" <cygwin AT cygwin DOT com>
Reply-To: "C. Linus Hicks" <linush AT mindspring DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

On the server side, you can update the sshd_config file and set the value of the ClientAliveInterval to a non-zero value, like 60 seconds. Or you can set the ServerAliveInterval option to a similar value in your client options, either on the command line or in your local config file.

-----Original Message-----
From: Soren <somian08 AT gmail DOT com>
Sent: Mar 28, 2025 2:25 PM
To: <cygwin AT cygwin DOT com>
Subject: sshd times out and disconnects client

Hello Cygwinstas,

I've got a question about the cygwin ssh daemon running on Windows. I don't
know if there is a setting in sshd or in Windows that would alter the
behavior I am seeing. That's what I am hoping for.

When logging in from a Linux system to my Windows 10 box, there's a timeout
(of what duration, I am not precisely sure, maybe after 2 hours?) if I am
not doing anything over the ssh connection. The session is disconnected at
the server end. I find this a bit annoying. I might want to be doing
something else for a couple hours and then come back to the session, only
to find it's disconnected. This is in contrast to the reverse case, where I
am logging in to one of my Linux boxes from Windows: in that case, the
connection stays alive until I deliberately close it. The same with
sessions between Linux machines. It's only in the case of incoming
connections to sshd on cygwin/windows that I am seeing this.

Insights greatly appreciated.
Regards,
Your fellow loyal Cygwinista, Soren Andersen

--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple



-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple