This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
SSH Tunneling and TCP_NODELAY
- From: Brian Genisio <briangenisio at yahoo dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 29 Oct 2002 14:06:37 -0800 (PST)
- Subject: SSH Tunneling and TCP_NODELAY
- Reply-to: brian at genisio dot org
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/