From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 07:15:08 2008 Return-Path: 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 07E491065688 for ; Thu, 13 Mar 2008 07:15:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id C34DF8FC25 for ; Thu, 13 Mar 2008 07:15:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id E8D0E41C7A6; Thu, 13 Mar 2008 08:15:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id rRKV5jZfZQpv; Thu, 13 Mar 2008 08:15:06 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id 0E0EE41C7B4; Thu, 13 Mar 2008 08:15:06 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 2C45644487F; Thu, 13 Mar 2008 07:14:14 +0000 (UTC) Date: Thu, 13 Mar 2008 07:14:14 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Mike Silbersack In-Reply-To: <20080312232607.J60219@odysseus.silby.com> Message-ID: <20080313071306.F50685@maildrop.int.zabbadoz.net> References: <20080312231330.D60219@odysseus.silby.com> <20080312232607.J60219@odysseus.silby.com> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, "d.s. al coda" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Mar 2008 07:15:08 -0000 On Wed, 12 Mar 2008, Mike Silbersack wrote: > > 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 1460,sackOK,eol,eol> > > 7.0: > IP A > B : S 3304309835:3304309835(0) ack 710421411 win 65535 1380,sackOK,eol,nop> > > That makes the problem quite a bit more clear. Anyone working on this issue > should apply this patch ASAP. While this makes it more clear I'd rather see things in hex after the first EOL but either way is fine, just to see it. Ideally tcpdump would also complain if any padding after EOL is not 0x00. I wonder if wireshark does? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time.