Date: Fri, 11 Feb 2005 10:15:35 +1300 From: Sam Jansen <sam@meta.net.nz> To: freebsd-net@freebsd.org Subject: SACK problems Message-ID: <420BCEF7.1080603@meta.net.nz>
index | next in thread | raw e-mail
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?
Cheers,
--
Sam Jansen sam@wand.net.nz
Wand Network Research Group http://www.wand.net.nz/~stj2
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?420BCEF7.1080603>