From owner-freebsd-net@FreeBSD.ORG Sun Mar 16 18:03:48 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 CB9461065675 for ; Sun, 16 Mar 2008 18:03:48 +0000 (UTC) (envelope-from coda.trigger@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id A93D68FC18 for ; Sun, 16 Mar 2008 18:03:48 +0000 (UTC) (envelope-from coda.trigger@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so5789814waf.3 for ; Sun, 16 Mar 2008 11:03:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=0RIohMyvNm7PnG1hzzTQRgrDeG6u1n+mKLiZwHqgG9o=; b=pOCGGW8t8QpQud1xYrNFauEVpaOga1yrOy3nD8LriTX42gV2iavfCk4ZhEE4LLxPCbhtUX8JJJz/dK2DGUpAyrdPWlsC0NxsvhJU0aB/FCyD1zktitZd1WE6NH7cOkDJ2t3tfoncw0u5SMNcMiwMQ+NlRUmYsE4W0oZ6Y/wRoMQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=eW3mlfWl+IzqOArkk5Ff7oYtJfwm5zRMk4MvpVBw7AX18ZIHhFXa9gq/BVKnnwDrikY3SZf15zY85+URgaTHT5tP3ieZosniWKI9f6Ft+uUQmLpckxgCArhSfNugIOyFUczDOts4IJgZ5XV21JtWYLi/4v/xjDAdEXWbOmSmcYA= Received: by 10.114.112.1 with SMTP id k1mr16321167wac.24.1205690628259; Sun, 16 Mar 2008 11:03:48 -0700 (PDT) Received: by 10.115.15.12 with HTTP; Sun, 16 Mar 2008 11:03:48 -0700 (PDT) Message-ID: Date: Sun, 16 Mar 2008 14:03:48 -0400 From: "d.s. al coda" To: "Andre Oppermann" In-Reply-To: <47D860AC.6030707@freebsd.org> MIME-Version: 1.0 References: <47D860AC.6030707@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Mar 2008 18:03:48 -0000 On 3/12/08, Andre Oppermann wrote: > > We've already fixed two issues. The first changes the order of the TCP > options > and is in this change: > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_var.h.diff?r1=1.160;r2=1.161 > > It is to solve a problem observed by ISC that sounds very much like what > you > describe. This fixed the issue in this case. Since this patch just has the effect of moving sackOK after the timestamps, it won't fix the problem that we were seeing, because it was occurring only in the absence of timestamps. > The second changes the alignment padding from NOP to 0x00. Whether this > was > a contributing factor to the reported problem is not clear. There hasn't > (yet) > been any specific test case for it. It was fixed because the RFC > specifies 0x00 > to be used for padding and nothing else. > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_output.c.diff?r1=1.145;r2=1.146 This looks promising. I didn't realize that the 0x01 padding was wrong since I didn't read the spec :) > It would be very helpful if you could apply these two patches after each > other > to your 7.0 test server and find out together with the affected user(s) > which > of these fixes the issue. If you can please try to test each one with and > w/o > the routers firewall enabled. It is interesting to know whether the NAT > or > firewalling part of the router chokes on it. I've applied the two patches and reversed mine (side note -- sadly, this is a production server, not a test server) . I'll let you know shortly whether we're still having problems, and I'll also try get the router info for you. -coda