search for: synack

...ust fine. It happened to my workstation, too, while having little traffic, so I scrambled at the linux box to see what happens to the packets. The debugging tool was IPTraf. I noticed the following: - SYN comes from the workstation, creates an entry in ip_conntrack, then goes on the internet - SYNACK comes from the internet, then disappears in the bowels of the kernel - another SYN for the same connection comes from the workstation, and is greeted with a SYNACK by the server which also disappears - finally, the workstation gets tired of waiting and the connecting application fails - several m...

...nd that: ;------------------Begin clipboard---------------------------- if (tcp_syncookies) sc->sc_iss = syncookie_generate(sc); else sc->sc_iss = arc4random(); ;--------------------End clipboard---------------------------- Is it the place where synack iss is generated? If yes, then why net.inet.tcp.syncookies sysctl is turned on by default? Is arc4random not enough random? Was there another reason to `request exact RFC 1948 compliance' by default? I am not just curious about that issue (although I _am_ curious :) ), but I am currnetly trying...

Hello All, We have a Linux cluster application that uses openssh as its inter-node communication mechanism and we've recently run into a problem that points to a potential scalability issue in openssh code. Our client nodes systematically open ssh connections to the server node to execute an administrative command. When establishing socket connections, the server side sometimes fails to

Hi. I don''t know if this one is known, but I can''t recall seeing anything about it. If it is old news I apologize. I discovered a bug in the inetd that comes with NetKit-B-0-08 and older. If a single SYN is sent to port 13 of the server, inetd will die of Broken Pipe: write(3, "Sun Jan 12 21:50:35 1997\r\n", 26) = -1 EPIPE (Broken pipe) --- SIGPIPE (Broken pipe) ---

TL;DR ----- In this RFC we propose the introduction of the concept of hardware socket offload to the Linux kernel. Patches will accompany this RFC in a few days, but we felt we had enough on the design to solicit constructive discussion from the community at-large. BACKGROUND ---------- Many applications within enterprise organizations suitable for virtualization neither require nor desire a

TL;DR ----- In this RFC we propose the introduction of the concept of hardware socket offload to the Linux kernel. Patches will accompany this RFC in a few days, but we felt we had enough on the design to solicit constructive discussion from the community at-large. BACKGROUND ---------- Many applications within enterprise organizations suitable for virtualization neither require nor desire a

Hi Everyone, This is off-topic, so please feel free to disregard it, but I'm sending it to this list in the hope that it will reach a largish number of users. I am currently looking at updating some of our advocacy material (which advertises exciting new features like SMP support), and before I do I'd like to get a better feel for why the rest of you are using FreeBSD. If you had to

If one is using the pidfile as an indicator of sshd's status, it is possible to kill sshd before the sigterm handler gets installed, since the pidfile is written out before the signal handlers are setup. The solution is to simply write the pidfile after the signal handlers are setup. Here's the patch. Rob --- sshd.c.orig Fri Jun 22 11:16:41 2001 +++ sshd.c Fri Jun 22 11:18:32 2001 @@

The byteorder detection macro for the rijndael algorithm doesn't work for systems that are building for multiple architectures, such as Darwin. This was the change that was needed to rijndael.c to get the macros building properly in such a situation. It seems to be a little more reliable than the existing system. Rob --- openssh_cvs/rijndael.c Tue Feb 27 13:14:22 2001 +++