DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 52SKTcix482935 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 52SKTcix482935 X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0A6653857BA5 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 0A6653857BA5 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1743193749; cv=none; b=FdkPFb3+R/uzLac/2WNnN1yOq40LMkxsicz363lJBApFU3Dc+tIouezRcrlEYn+eo9cxHkWo4i1ePS8kz6XmmjOJlAQsayv4f2+94HYAwCWwCQ0GTuBvJnnJ3gG2I/rJvvFJMZT4e7q/G/eVW9/Jbn+cg9Y6GNLSAPRFp8y4Hyc= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1743193749; c=relaxed/simple; bh=xnzxKexTWpnmDZ51F7FUYqthdfVvxFqbd9nHlTBOYL4=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=rTRSLZp6/uj3vaggmTGTY6ZxvsaLEtkIjvIAMUqBETAKqq92IaMFEhao/YnB3wkW3ssdzcxXOXU/ZvkNdNDyWi3jSRri/xkssM5a8WNDlJqclJ/or+2vC1Slc2DUaLRnzrvzr0KlMA+LHBQH2U9AxbWNUeao44IjTNNwxLTvG78= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0A6653857BA5 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1743193739; x=1743798539; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=o4pjG7AzpSXYUDX2j48535ULuHMGmhk8JWBP8CK5ivs=; b=emoYYO4Wm2hGli6YJxeY8xBl48fhRRWIqK1FN9nbs4MkZNNYHX497VAPAC2VNxqQEA 9KPT/9diuvfZNRGs1wpGzh3uwSsE0qEqUZwIQ3zw1d8hGZPgJGyVK9tO137UH6rI7Lih 0iduC9X4iT85y3nsBHFi9GeNwPzPu56fs6wkTvZ8CDHXFmISs/xPoM9+P+qyUdRLA7tc QPFToSPEIZxDmbX7bz0wRmvvgWO6l6S/lXka3YIquYhK4uXmAYvGRXhTfSI9OJSRI3Zx L+gUsWUBuXiMA7H4nzw7BPfU/Z47SFz5+Ggp06x8072ezQcsGgMxF6jkYVBX7G3yvhdE caKw== X-Gm-Message-State: AOJu0YwKRSPMMFa+dg4oswbipLe9P2hIJ1bBH1R2w6mwrpVhaygvoLyw M+UVyk0ohLEL7IeZG7wrnSOctmPcdgjumy+ROqaL+T8tVmLcFWgBQNnQFxKsT5ArW7Bl7nTpLw0 MehzKXNWpfZJWUGKBkYPovsMRDvI= X-Gm-Gg: ASbGncufscY8/MdlXUYXfFyoX6SDI4YfePV63j/IykyTvAZznNUFt52CBkyZVCBaWF9 RFjaJPcb0eM8mBlEl1ZF1BbYF1oCpEQUObm+q62LfNwy2fUgnZ0Hn/3l6Ja/aEhJD0YIARNnE+a hrimoovq9GDHO7nzElP0+NhU4= X-Google-Smtp-Source: AGHT+IFT/aDNZQ3K+B1az48ylFASFw1ytGtMT2HWco2yiEymy3CM1nQuY6066lTfPZiEzp/9Sf4tLtiAue5aSr/WtNQ= X-Received: by 2002:a05:651c:199e:b0:308:f787:5c48 with SMTP id 38308e7fff4ca-30de034a7c3mr2694131fa.33.1743193738748; Fri, 28 Mar 2025 13:28:58 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 28 Mar 2025 16:28:44 -0400 X-Gm-Features: AQ5f1JqgP8_J-AfYs_wVTjMtkogoUe-OrB91NtT9j8EBd9Kd4vyuvjzwA4l-vrE Message-ID: Subject: Re: sshd times out and disconnects client To: "C. Linus Hicks" Cc: cygwin AT cygwin DOT com X-Content-Filtered-By: Mailman/MimeDel 2.1.30 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Soren via Cygwin Reply-To: Soren Content-Type: text/plain; charset="utf-8" Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 52SKTcix482935 Hello Linus H. and others, Ok! The quick reply was especially helpful today. Thanks very much, Linus, for the expert advice! I edited /etc/sshd_config according to your information and stopped and restarted sshd. Then logged in from a Linux box and all seems well. Cygwin still rocks. Soren Andersen On Fri, Mar 28, 2025 at 2:42 PM C. Linus Hicks wrote: > 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 > Sent: Mar 28, 2025 2:25 PM > To: > 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