Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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:	<48270-220021033002139858@M2W034.mail2web.com>
X-Priority:	3
Reply-To:	lhall AT rfk DOT com
X-Originating-IP:	209.113.174.244
From:	"lhall AT pop DOT ma DOT ultranet DOT com" <lhall AT pop DOT ma DOT ultranet DOT com>
To:	brian AT genisio DOT org, cygwin AT cygwin DOT com
Subject:	RE: SSH Tunneling and TCP_NODELAY
Date:	Tue, 29 Oct 2002 19:21:39 -0500
MIME-Version:	1.0
X-OriginalArrivalTime:	30 Oct 2002 00:21:39.0814 (UTC) FILETIME=[50E4E060:01C27FAA]
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g9U0LxQ16572

So this is a Cygwin issue and not a ssh issue (i.e. you're saying
it works fine if the Cygwin ssh isn't in the loop)?

Larry

Original Message:
-----------------
From: Brian Genisio briangenisio AT yahoo DOT com
Date: Tue, 29 Oct 2002 14:06:37 -0800 (PST)
To: cygwin AT cygwin DOT com
Subject: SSH Tunneling and TCP_NODELAY


Hi all,

I am using SSH port forwarding on a linux sshd from the Cygwin ssh.  Both
sides
have version OpenSSH 3.4p1.  There is no problem with my tunneling, as I
have
been using many (about 10) port forwards (server and local) for quite some
time
now.

A new application has been introduced to my mix that uses the network to
send
control messages at about 30 times per second.  These messages are small
(4-12
bytes), but sent at a frequent rate.

If port forwarding is NOT used, the control stream is working well.  BUT,
if I
send the control string through the SSH tunnel, it gets sent as bursts...
for
example, the receiving application wukk get no data for 5 frames, and the
6th
frame will get all 6 frames.

This makes for a jerky control of the software.  My control program has
TCP_NODELAY set in it's ouput socket which is why it works properly.  I
_thought_ that openssh starting at version 3.1 had TCP_NODELAY set on it's
forwarded ports (my debug outputs tell me so).  None the less, the bursting
(which I believe is a cacheing at some point) still happens.

My question:

Is there something about the Cygwin version of SSH where TCP_NODELAY doesnt
work properly, or it is a stub function?  Can anyone think of a reason this
is
happening?

Thanks,
Brian

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -