Date: Thu, 10 Feb 2005 13:28:52 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Sam Jansen <sam@meta.net.nz> Cc: freebsd-net@freebsd.org Subject: Re: SACK problems Message-ID: <20050210212852.GA10195@xor.obsecurity.org> In-Reply-To: <420BCEF7.1080603@meta.net.nz> References: <420BCEF7.1080603@meta.net.nz>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Fri, Feb 11, 2005 at 10:15:35AM +1300, Sam Jansen wrote: > During some testing on an isolated network we have, I found some > interesting behaviour from a FreeBSD 5.3 host using TCP SACK. > > I've detailed this problem fully at: > > http://www.wand.net.nz/~stj2/nsc/emu_freebsd.html > > PCAP traces and some screenshots from tcptrace graphs can be found at > the above link to show what is happening. It looks to me like SACK > blocks are being incorrectly generated in this example. I can't think of > any valid reason why a SACK block would SACK from below the current ACK > value to above it (which is the problem here). > > Thoughts, anyone? Am I just wrong here and this is valid, expected > behaviour? A fix to the SACK code was committed yesterday, which may or may not be relevant. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCC9IUWry0BWjoQKURAnpyAJ9Z8R6ydGjhdKCqpt+zPuCC/0K9qACePnEX D/fZFvFAiL1m8Af2l+pMJjg= =kW8D -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050210212852.GA10195>