From owner-freebsd-net@FreeBSD.ORG Thu Mar 13 04:57:36 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 2A58D1065670 for ; Thu, 13 Mar 2008 04:57:36 +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 C87BE8FC13 for ; Thu, 13 Mar 2008 04:57:35 +0000 (UTC) (envelope-from silby@silby.com) Received: (qmail 63299 invoked from network); 13 Mar 2008 04:57:35 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 13 Mar 2008 04:57:35 -0000 X-pair-Authenticated: 209.68.2.70 Date: Wed, 12 Mar 2008 23:57:34 -0500 (CDT) From: Mike Silbersack To: "Bjoern A. Zeeb" In-Reply-To: <20080312144207.P50685@maildrop.int.zabbadoz.net> Message-ID: <20080312235523.I60219@odysseus.silby.com> References: <20080312144207.P50685@maildrop.int.zabbadoz.net> 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 04:57:36 -0000 On Wed, 12 Mar 2008, Bjoern A. Zeeb wrote: > On Tue, 11 Mar 2008, d.s. al coda wrote: > >> - FreeBSD 7 has (there is of course an aligning nop >> after the eol, which tcpdump skips) > > Which is a bug (the nop after the EOL) that I recently fixed in HEAD. > I am still curious to know if it's only ordering or the invalid padding > or both that keeps clients from connecting. The problem is getting > hands on such a problematic "client". Bjoern, can you get that fix MFC'd ASAP? I've e-mailed a tcpdump developer asking how we can enhance it so that it prints out <..., eol, nop> so that we can detect such errors more easily in the future. I wish I had paid more attention to that part of the previous thread on this topic! -Mike