From owner-freebsd-net@FreeBSD.ORG Fri Mar 21 02:09:50 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 DC881106566C for ; Fri, 21 Mar 2008 02:09:50 +0000 (UTC) (envelope-from coda.trigger@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mx1.freebsd.org (Postfix) with ESMTP id A5A278FC15 for ; Fri, 21 Mar 2008 02:09:50 +0000 (UTC) (envelope-from coda.trigger@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1313380waf.3 for ; Thu, 20 Mar 2008 19:09:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=SzfeHM9jS239MzQL1JYoF69i9FuL1WNVxKFIiFmcY1M=; b=RGJUsDrtPOkGNh0lhMd99rAeqiloYd6oUL9rS+RhE4wPBVmi6YsU/cKvLlcCVdlyid++IasyvU8+qowJwPJMKI+dU6uhQhESOXWLk+YGefYVfNRjysgLK7/WMtkv7KzpaBNdOB4tc1fzG35qxvlspJi6kC7Psq2m1eCS6m7Snbw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=JanaEUK13ytlL/lQq/A9mYLb7EDNxUGvnq3gGybPcG4p/wD0rLklu5wq61JBg1vLO2teVCklv4XuPn9flk3IwnwyKWdurHUGzyzFNKLYQiLuoQ30QM1ji8QUfUHZfusHsgVFtlqq9OuzBTJA0JfWOitQPXWgvOQEyIviKbZ/yBE= Received: by 10.114.134.20 with SMTP id h20mr4892930wad.91.1206065389937; Thu, 20 Mar 2008 19:09:49 -0700 (PDT) Received: by 10.114.73.4 with HTTP; Thu, 20 Mar 2008 19:09:49 -0700 (PDT) Message-ID: Date: Thu, 20 Mar 2008 22:09:49 -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: Fri, 21 Mar 2008 02:09:51 -0000 On 3/12/08, Andre Oppermann wrote: > > I'd be very interesting to know the exactly models and their firmware > version > of the affected routers. If available locally I'd like to obtain a > similar > model myself for future regression tests. Here are the models we managed to hear about via email: D-Link WBR-1310 Linksys WCG200 (with firewall enabled) Encore Broadband Router Linksys WAG354G Ambit U10C019 Netgear CG814GCMR We didn't get any firmware version info that I know of. Hope this is still helpful. > > 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. > > 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 > > 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. > > We've been running with the patches for a few days now, and they seem to fix the issue. We checked with one previously-affected user, and we haven't received any reports of problems. -coda