Displaying 20 results from an estimated 3000 matches similar to: "TCP_NODELAY in Cygwin port"
2003 May 07
4
[Bug 556] TCP_NODELAY not set completely for port forwarding
http://bugzilla.mindrot.org/show_bug.cgi?id=556
Summary: TCP_NODELAY not set completely for port forwarding
Product: Portable OpenSSH
Version: -current
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo: openssh-unix-dev at mindrot.org
2003 Oct 26
1
getsockopt TCP_NODELAY: Socket operation on non-socket
We get the warning above whenever we use a ProxyCommand. We _know_ it's
a pipe, so we can't use sockopts on it. So we shouldn't bitch about it.
This breaks all kinds of things which use SSH transparently; including
pine, which really wants the first thing it receives from an IMAP server
to be a valid imap greeting... which $subject is not.
$ ssh -o "proxycommand sh -c '(
2003 Aug 26
2
[Bug 556] TCP_NODELAY not set completely for port forwarding
http://bugzilla.mindrot.org/show_bug.cgi?id=556
------- Additional Comments From markus at openbsd.org 2003-08-27 02:56 -------
sshd already sets nodelay for the connection, but conditionally, and
only for interactive sessions, so this is the well known problem:
why does sshd traditionally set no delay only for interactive sessions.
------- You are receiving this mail because: -------
2003 May 09
2
TCP_NODELAY always set, now?
I know that there was a discussion on this about a year back, and
there is a bug 556 this week that mentions TCP_NODELAY.
However, when I use ssh through a pipe (e.g., to tunnel through an
HTTP proxy using CONNECT) I see:
getsockopt TCP_NODELAY: Socket operation on non-socket
How do I tell which end is generating this (I'm assuming the local
side, which is running through the pipe).
Also,
2003 May 06
0
OpenSSH Bug / Fix
To Whom It May Concern,
Our team has found what we believe to be a bug in the code for SSHD. When
creating an SSH port forward between a Linux machine (server) and a machine running
Cygwin (client), we were getting buffering of data coming from the server. This buffering
caused small ammounts of data to be bursted, instead of sent immediately. Also, since
debug output showed that
2007 Sep 20
2
Search::Xapian cygwin fix
Olly,
The cygwin linker requires -shared, otherwise WinMain at 16 will not be skipped.
BTW: mingw also. But this should test and fix someone else.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
http://spacemovie.mur.at/ http://helsinki.at/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Search-Xapian-1.0.2.0-cyg.patch
Type:
2004 Oct 27
1
Slow uploading with sftp
Hi,
I'm observing a nasty and strange behaviour with OpenSSH
(SSH-2.0-OpenSSH_3.7.1p2) on Solaris 8 (Sparc). I searched the FAQ and
list archive and I didn't find anything about it.
The problem is that uploading through sftp is tremendously slow (~
0.2KB/s) while downloading is ok (~ 200-300 KB/s), so I'm quite surprised.
The machines I tested (client & server) are all in the
2003 May 10
1
OpenSSH_3.6.1p2 getsockopt TCP_NODELAY bogus message on Solaris 8
I ran into the following problem the first time I used
OpenSSH_3.6.1p2 on Solaris 8 (sparc, 32-bit):
$ ssh kiwi
Enter passphrase for RSA key '/net/sic/export/ford/home/eggert/.ssh/identity':
getsockopt TCP_NODELAY: Socket operation on non-socket
Last login: Sat May 10 14:27:01 2003 from ip-66-80-53-59.d
Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
2005 Dec 28
2
Use of TCP_CORK instead of TCP_NODELAY
Klaas Jan Wierenga wrote:
> Hi Henri and others,
>
> Very interesting post about TCP_CORK. I would be very interested in having
> it applied in the next version of Icecast.
I'd be more interested in some figures to show there being a benefit,
most examples talk about HTTP servers with short lived connections where
sendfile(2) is used.
> For low-bitrate streams the problem
2005 Dec 29
0
Use of TCP_CORK instead of TCP_NODELAY
> This is exactly why it was implemented, a few people complained about
> the overhead with large numbers of listeners, not only because of the
> TCP overhead but also the fact that it reduces the write syscall
> overhead. Will TCP_CORK (linux) and TCP_NOPUSH (BSD) give noticable
> benefits wrt icecast? It might prove helpful if available but more info
> is needed.
As
2005 Dec 29
1
Use of TCP_CORK instead of TCP_NODELAY
Klaas Jan Wierenga wrote:
>>This is exactly why it was implemented, a few people complained about
>>the overhead with large numbers of listeners, not only because of the
>>TCP overhead but also the fact that it reduces the write syscall
>>overhead. Will TCP_CORK (linux) and TCP_NOPUSH (BSD) give noticable
>>benefits wrt icecast? It might prove helpful if available but
2013 Aug 18
4
[Bug 2016] SCTP Support
https://bugzilla.mindrot.org/show_bug.cgi?id=2016
openssh at ml.breakpoint.cc changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |openssh at ml.breakpoint.cc
--- Comment #5 from openssh at ml.breakpoint.cc ---
The link local address (fe80::) require the
2003 Jun 24
8
[Bug 602] enormous bitching about netdb.h
http://bugzilla.mindrot.org/show_bug.cgi?id=602
Summary: enormous bitching about netdb.h
Product: Portable OpenSSH
Version: 3.6.1p2
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Build system
AssignedTo: openssh-bugs at mindrot.org
ReportedBy: tedm at
2006 Mar 12
3
[Bug 981] Flow stop in SSH2
http://bugzilla.mindrot.org/show_bug.cgi?id=981
djm at mindrot.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #811| |ok+
Flag| |
------- Comment #6 from djm at mindrot.org 2006-03-12 16:16 -------
(From update
2005 Apr 12
7
Samba question
1. Does anyone know what may be happening here? When I try to map a
drive from a PC, I get the following error: "The account is not
authorized to log in from this station.". I can map the drive just fine
from my PC. Does anyone know what may be going on here? Any help would
be greatly appreciated.
2. Also, whenever I use SWAT, it takes a long time for the
information to be
2002 Oct 17
0
Upgraded to latest cygwin this morning, and ssh refuses to enter binmode. Help! (fwd)
Could someone running Cygwin or involved in Cygwin help this person
please?
- Ben
---------- Forwarded message ----------
Date: Thu, 17 Oct 2002 17:58:45 -0400
From: Andrew Greene <agreene at pageflexinc.com>
To: openssh at openssh.com
Subject: Upgraded to latest cygwin this morning,
and ssh refuses to enter binmode. Help!
I upgraded to the latest cygwin this morning (not sure when
2003 Dec 31
0
Problem with port forwarding on Mac OS X
I have found a problem with port forwarding on Mac OS X (10.2 and
10.3). When I forward
a port to localhost, as in
ssh -R 40404:localhost:40404 somehost
...and the remote system makes a connection on this port, I get the
message
getsockopt TCP_NODELAY: Connection reset by peer
I have tracked this down to the loop in connect_to that gets a list of
addresses from
getaddrinfo and tries them
1998 Sep 20
0
Unknown socket option TCP_NODELAY
I am trying to get Samba to work on my RedHat 5.0 machine. I got it to the
point where i could see the RedHat server from Windows 95 but could access
the file system. It gave me messages about the server
being busy. Now I can not see the server from windows 95. If I do a
net view \\monster1 I get the following error messag
Error 54: The network is currently busy processing other requests
or is
2002 Jan 03
0
TCP_NODELAY or not
Hi,
Why not turn off TCP_NODELAY in OpenSSH, atleast in the server->client
direction? If a user is doing 'ls -l' over an Internet link that has
some latency, he/she is flooded with a burst of small packets that
can cause congestion and packet loss.
Quite many people have been noticing this behaviour when doing ls -l
resulting in <output> <delay> <output>
2002 Jan 31
1
Use of TCP_NODELAY in commercial SSH
In order to test my overlapping request path for sftp on another ssh
server, I downloaded ssh2 version 3.1.0 from ssh.com. Having downloaded
it, I decided to study the use of TCP_NODELAY in that implementation.
Here's what I found:
* Both ssh2 and sshd2 has a NoDelay config option which is false by
default.
* The ssh2 client does not enable or disable NoDelay because of a channel