Date: Mon, 8 Apr 1996 01:13:56 +0200 (MET DST) From: =?iso-8859-1?Q?=22=C5ge?= =?iso-8859-1?Q?R=F8bekk=22?= <aagero@aage.priv.no> To: freebsd-bugs@freebsd.org Subject: tcp extensions broken in current? Message-ID: <199604072313.BAA11683@birk04.studby.uio.no>
next in thread | raw e-mail | index | archive | help
It appears to me, after comparing -current and -stable, that the tcp extensions behave differently and not as expected in -current. The most apparent and noticeable situation is a finger client request to a linux box. This is when net.inet.tcp.rfc1644 is set. This might indicate potential problems with other tcp clients too, with a not so easy interface and therefore not so easy to spot. But on the other hand, it can also mean that the rfc1644 extension has been enhanced, and the linux tcp stack has always been broken in this manner, but noticable first after this change. I haven't been able to compare tcpdump output from a -stable and a -current host though. -aage
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604072313.BAA11683>