search for: tcp_nodelays

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

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 '(

> > p.s. For an in depth analysis of TCP_CORK read Christiopher Baus' excelent > article: http://www.baus.net/on-tcp_cork Thanks for this pointer. I'd been meaning to reply on this thread, but hadn't got around to it, primarily because I didn't really understand TCP_CORK (the linux manpage is, as usual, fairly unclear on what exactly it does). Now I understand! > >

Hello SSH developers, I am sorry if this is not really a bug, and I am missing something, but I am running into an issue with port forwarding in SSH. I am using 3.4p1 of SSH on both sides. I am running the ssh daemon on a Slackware Linux 8.0 machine, and the ssh client is running in Cywgin version 1.3.13. The ssh client is creating about 7 port forwards in a mix of local and remote forwarding

https://bugzilla.mindrot.org/show_bug.cgi?id=2124 Bug ID: 2124 Summary: TCP_NODELAY not set by sshd for non-interactive non-exec sessions Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 Component: sshd

Hello, I found the folloing message in log.smbd [2001/04/18 13:00:41, 0] lib/util_sock.c:set_socket_options(165) Failed to set socket option SO_KEEPALIVE (Error Bad file number) [2001/04/18 13:00:41, 0] lib/util_sock.c:set_socket_options(165) Failed to set socket option TCP_NODELAY (Error Socket operation on non-socket) so I searched TCP_NODELAY in the INCLUDEFILES: (/usr/include/sys) >

Michael, With regard to your comment below: > As a streaming server, it's fairly crucial for icecast to send out > data with as low a delay as possible (many clients don't care, but > some do). That's why we use TCP_NODELAY - we actually WANT to send out > data as soon as we can. Can you explain how some clients depend on a low delay when receiving data from icecast? How

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,

We're abusing icecast in a true narrowcasting setup (personalized stream per mountpoint). The streams itself are created in a piece of proprietory (spelling?, i'm dutch) software, icecast merely relays them. However, the intended endpoint is an embedded device. This device has trouble with tcp/ip packets not matching the max. packet size (MSS or MSS minus header). After eleborate testing,

I'm not sure the user would know ;). This is very system-specific issue just because the Linux network stack behaves so differently from other OSes (for purely historical reasons). That makes it hard to abstract as a "feature" for the R sockets that are supposed to be platform-independent. At least TCP_NODELAY is actually part of POSIX so it is on better footing, and disabling

On Fri, Mar 24, 2023 at 02:41:20PM -0500, Eric Blake wrote: > On Fri, Mar 24, 2023 at 11:47:20AM +0100, Florian Westphal wrote: > > qemu-nbd doesn't set TCP_NODELAY on the tcp socket. Replying to myself, WHY aren't we setting TCP_NODELAY on the socket? > > And surprisingly, qemu IS using corking on the client side: >

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

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

smbclient is broken if TCP_NODELAY is enabled. I am running FreeBSD 2.2.7 Stable. 1. Enable socket options = TCP_NODELAY 2. Run smbclient to access a share on a Win95 box 3. Turn 'recurse' on 4. cd to a directory that contains one directory and no files 5. Do a dir 6. The files which live in the directory below the default directory will not be seen. 7. Eliminate TCP_NODELAY and they

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

On Mon, 2 Nov 2020 at 02:22, Simon Urbanek <simon.urbanek at r-project.org> wrote: > > It looks like R sockets on Linux could do with TCP_NODELAY -- without (status quo): How many network packets are generated with and without it? If there are many small writes and thus setting TCP_NODELAY causes many small packets to be sent, it might make more sense to set TCP_QUICKACK instead.

In certain situations sftp download speed can be much less than that of scp. After many days of trying to find the cause finally I found it to be the tcp nagle algorithm, which if turned off with TCP_NODELAY eliminates the problem. Now I see it being discussed back in 2002, but it still unresolved in openssh-4.2 :( Simple solution would be to add a NoDelay option to ssh which sftp would set.

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'm using Icecast in a somewhat narrowcasting setup with large numbers of sources (> 100) and between 5 and 50 listeners per source. All streaming is done at low bitrates (16 - 24 kbit/sec) and listeners use embedded devices connected by 56k modems. It

Hi, I run a Veritas cluster server with two different samba's 2.0.7 compiled with SUNWspro 4.0 (gcc 2.95 leads to the same results) on Solaris 7 UltraSPARC 60 server. One compiled with --prefix=/opt/samba-test the other with --prefix=/opt/samba-eng. To avoid using 127.0.0.1 or 0.0.0.0 when both smbd's running on the same cluster host I set this in both smbd.conf

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: -------