From owner-freebsd-net@FreeBSD.ORG  Thu Mar 13 04:28:49 2008
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5C2BE1065672
	for <freebsd-net@freebsd.org>; Thu, 13 Mar 2008 04:28:49 +0000 (UTC)
	(envelope-from silby@silby.com)
Received: from relay03.pair.com (relay03.pair.com [209.68.5.17])
	by mx1.freebsd.org (Postfix) with SMTP id F3D958FC14
	for <freebsd-net@freebsd.org>; Thu, 13 Mar 2008 04:28:48 +0000 (UTC)
	(envelope-from silby@silby.com)
Received: (qmail 59568 invoked from network); 13 Mar 2008 04:28:47 -0000
Received: from unknown (HELO localhost) (unknown)
	by unknown with SMTP; 13 Mar 2008 04:28:47 -0000
X-pair-Authenticated: 209.68.2.70
Date: Wed, 12 Mar 2008 23:28:46 -0500 (CDT)
From: Mike Silbersack <silby@silby.com>
To: "d.s. al coda" <coda.trigger@gmail.com>
In-Reply-To: <20080312231330.D60219@odysseus.silby.com>
Message-ID: <20080312232607.J60219@odysseus.silby.com>
References: <f90b44e40803111756h517b373ala8afdff9395b7fac@mail.gmail.com>
	<20080312231330.D60219@odysseus.silby.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED;
	BOUNDARY="1861302967-1271846343-1205382526=:60219"
Cc: freebsd-net@freebsd.org
Subject: Re: TCP options order changed in FreeBSD 7, incompatible with some
 routers
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Mar 2008 04:28:49 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1861302967-1271846343-1205382526=:60219
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed


On Wed, 12 Mar 2008, Mike Silbersack wrote:

> I think we will need to fix tcpdump before trying to finish diagnosing this 
> problem.  We were missing key information before.
>
> -Mike

Hm, that was far easier than expected.  Patch attached.

Here's what the two tcpdumps show now:

6.3:
IP A > B : S 2575736483:2575736483(0) ack 1762868649 win 65535 <mss 1460,sackOK,eol,eol>

7.0:
IP A > B : S 3304309835:3304309835(0) ack 710421411 win 65535 <mss 1380,sackOK,eol,nop>

That makes the problem quite a bit more clear.  Anyone working on this 
issue should apply this patch ASAP.

-Mike
--1861302967-1271846343-1205382526=:60219
Content-Type: TEXT/PLAIN; charset=US-ASCII; name=tcpdump-opt_past_eol.patch
Content-Transfer-Encoding: BASE64
Content-ID: <20080312232846.R60219@odysseus.silby.com>
Content-Description: 
Content-Disposition: attachment; filename=tcpdump-opt_past_eol.patch

LS0tIHByaW50LXRjcC5jLm9sZAkyMDA4LTAzLTEyIDIzOjIxOjUyLjAwMDAw
MDAwMCAtMDUwMA0KKysrIHByaW50LXRjcC5jCTIwMDgtMDMtMTIgMjM6MjQ6
NTAuMDAwMDAwMDAwIC0wNTAwDQpAQCAtNjM3LDggKzYzNywxMCBAQA0KIAkJ
CWlmIChkYXRhbGVuICE9IGxlbikNCiAJCQkJKHZvaWQpcHJpbnRmKCJbbGVu
ICVkXSIsIGxlbik7DQogCQkJY2ggPSAnLCc7DQorI2lmIDANCiAJCQlpZiAo
b3B0ID09IFRDUE9QVF9FT0wpDQogCQkJCWJyZWFrOw0KKyNlbmRpZg0KIAkJ
fQ0KIAkJcHV0Y2hhcignPicpOw0KIAl9DQo=

--1861302967-1271846343-1205382526=:60219--