Date: Mon, 3 Oct 2005 18:06:39 +0100 (BST)
From: Martin Drallew <m.drallew@fatsquirrel.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Connection reset by peer - TCP window size oddity ?
In-Reply-To: <Pine.GSO.4.61.0510031241580.29231@scorpio.gold.ac.uk>
Message-ID: <Pine.GSO.4.61.0510031753020.29714@scorpio.gold.ac.uk>
References: <Pine.GSO.4.61.0510031241580.29231@scorpio.gold.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1046
Lines: 21

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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/