Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <410730CA.9020701@hot.ee> Date: Wed, 28 Jul 2004 07:51:22 +0300 From: Float User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: BUG: ssh.exe ProtocolKeepAlives option broken Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at neti.ee |>Summary: Cygwin ssh.exe doesn't accept the 'ProtocolKeepAlives' option |> |>Example: |>C:\sshclient>ssh -o ProtocolKeepAlives=180 example.com |>command-line: line 0: Bad configuration option: ProtocolKeepAlives | |AFAICT, ProtocolKeepAlives is not mentioned in the manpage for ssh. |So, this isn't a bug. Indeed, it seems that it is not mentioned in the Cygwin ssh_config manpage. However, that option should be supported according to the following Corinna Vinschen mail: http://sources.redhat.com/ml/cygwin/2002-01/msg00323.html Btw, the ProtocolKeepAlives is a must for using ssh for port forwarding behind a firewall that drops inactive connections. Regards, float -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/