Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<01fc01bfdf94$2df83ba0$4046fcc2@kuusnepa>
From:	"Tero Hilpinen" <tero DOT hilpinen AT sonera DOT com>
To:	<cygwin AT sourceware DOT cygnus DOT com>
Subject:	OpenSSH-2.1.0p3 and broken pipes
Date:	Mon, 26 Jun 2000 20:19:31 +0300
Organization:	Sonera Corporation
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2919.6700

It seems that the version of OpenSSH mentioned in the subject has
problems handling high speed traffic together with port forwarding.
Opening a connection between an OpenSSH client and daemon with several
forwarded ports and stressing the connection with a continuous data
stream, the shell access to the remote system running the daemon usually
dies and comments "Broken pipe". Surprisingly the forwarded ports still
work though.

I've made the classical mistake of upgrading too many system components
at the same time so I cannot be sure that this problem is caused by
OpenSSH. NT4.0/b20/Ophapkin-port of the original 1.2.2x worked ok - this
problem appears in my current W2K/1.1.2/2.1.0p3 setup. Some persons have
also commented that this might be a problem in OpenSSH itself, not just
in the Cygwin port.




--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -