From owner-freebsd-current Mon Feb 17 5:15:13 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 483DB37B401 for ; Mon, 17 Feb 2003 05:15:12 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id D60AF43F93 for ; Mon, 17 Feb 2003 05:15:11 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0008.cvx21-bradley.dialup.earthlink.net ([209.179.192.8] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18kl6v-0000xZ-00; Mon, 17 Feb 2003 05:15:06 -0800 Message-ID: <3E50E009.F8F41BE2@mindspring.com> Date: Mon, 17 Feb 2003 05:13:45 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: ticso@cicely.de Cc: Alastair D'Silva , freebsd-current@FreeBSD.ORG Subject: Re: Libalias Corruption References: <1045398012.846.21.camel@picard> <20030217102019.GF98225@cicely8.cicely.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4621ddb3e7b4064500c9304e271f89aa0350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bernd Walter wrote: > On Sun, Feb 16, 2003 at 11:20:13PM +1100, Alastair D'Silva wrote: > > I've had a weird problem since installing 5-CURRENT on my gateway, > > traffic originating from the gateway is fine, as is UDP from the > > unregistered network behind it, however, TCP traffic from the > > unregistered network is dropped. > > > > It seems that natd/libalias is corrupting the tcp header. > > I've noticed the same with source from 2003-02-08. > Before I was running 2002-12-27. > Replacing natd with an older version worked. > I can see translated tcp packets going out and the answers are > translated back by natd, but not reinjected into my ipfw rules. I pointed this out before; the IP checksum update is using the old RFC, not the new one, so it occasionally gets 0x0000 when it should get 0xffff (one's complement vs. two's complement). This gets really obvious really quickly when you put in a printf that spits when it sees a bad checksum (before and after). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message