From: Graham Murray <graham@gmurray.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Connection reset by peer - TCP window size oddity ?
References: <Pine.GSO.4.61.0510031241580.29231@scorpio.gold.ac.uk>
Date: Mon, 03 Oct 2005 15:44:13 +0100
In-Reply-To: <Pine.GSO.4.61.0510031241580.29231@scorpio.gold.ac.uk> (Martin
	Drallew's message of "Mon, 3 Oct 2005 12:56:20 +0100 (BST)")
Message-ID: <87r7b2k6de.fsf@newton.gmurray.org.uk>
User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 929
Lines: 18

Martin Drallew <m.drallew@fatsquirrel.org> writes:

> A tcpdump follows and, unless I'm misunderstanding the output (quite
> possible) it looks like the kernel is sending outside of the peer's
> TCP window, to which the peer responds by resetting the connection.

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.
-
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/