> 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
I experienced the same phenomenon. When TCP reassembly queue exceed
> 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
No. That fix is not relevant.
I'll take a look at this in a bit (after I fix the other SACK
issue reported a couple of days ago).
mohan
--- Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 11, 2005 at 10:15:35AM +1300, Sam Jansen wrote:
> > During some testing on an isolated network we ha
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
>
> PC