Graham Murray <graham@xxxxxxxxx> writes:
I think that you have overlooked one detail in the output. Both
systems have declared window scaling of 2, so when otter sets the
window size of 1984 in the packet it is actually advertising a window
of 7936, which you are not exceeding. You do not say what type of
system otter is (or what OS it is running), so one explanation is that
otter has just mirrored your 'wscale 2' in its SYN-ACK without
actually meaning it.
You're absolutely right of course, not a kernel bug, just dimwittedness
on my part. Turning off window scaling does seem to be an effective workaround.
Judging from a quick Google it seems there is still a lot of kit out there
that breaks window scaling :(
Many thanks for this and thanks to everyone that replied.
Martin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
