From owner-freebsd-current@FreeBSD.ORG  Tue Nov 25 17:07:52 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 9D08216A4CE; Tue, 25 Nov 2003 17:07:52 -0800 (PST)
Received: from perrin.nxad.com (internal.nxad.com [69.1.70.251])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E337043FE5; Tue, 25 Nov 2003 17:07:50 -0800 (PST)
	(envelope-from sean@nxad.com)
Received: by perrin.nxad.com (Postfix, from userid 1001)
	id B96C4212AB; Tue, 25 Nov 2003 17:06:55 -0800 (PST)
Date: Tue, 25 Nov 2003 17:06:55 -0800
From: Sean Chittenden <sean@chittenden.org>
To: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Message-ID: <20031126010655.GB19485@perrin.nxad.com>
References: <m3brr0x8d7.fsf@merlin.emma.line.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m3brr0x8d7.fsf@merlin.emma.line.org>
X-PGP-Key: finger seanc@FreeBSD.org
X-PGP-Fingerprint: 3849 3760 1AFE 7B17 11A0  83A6 DD99 E31F BC84 B341
X-Web-Homepage: http://sean.chittenden.org/
User-Agent: Mutt/1.5.4i
cc: freebsd-current@freebsd.org
Subject: Re: IPFW2 verrevpath issue (IPv4 TCP, fresh kernel)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Nov 2003 01:07:52 -0000
X-List-Received-Date: Wed, 26 Nov 2003 01:07:52 -0000

> Is my expectation wrong or is there a pertinent IPFW2 bug in a current
> 5.2-BETA kernel?

You're alone in this, though cjc hasn't been able to reproduce this.
Are you on a multi-homed system?  -sc

-- 
Sean Chittenden