From owner-freebsd-current@FreeBSD.ORG Wed Jun 23 15:57:06 2004 Return-Path: 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 DF54C16A4CE for ; Wed, 23 Jun 2004 15:57:06 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BD3C43D5E for ; Wed, 23 Jun 2004 15:57:06 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pandora.afflictions.org (Postfix) with ESMTP id 7192278C7C for ; Wed, 23 Jun 2004 11:58:29 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 7C687170C6; Wed, 23 Jun 2004 11:57:02 -0400 (EDT) Date: Wed, 23 Jun 2004 11:57:02 -0400 From: Damian Gerow To: current@freebsd.org Message-ID: <20040623155702.GD52737@afflictions.org> Mail-Followup-To: current@freebsd.org References: <20040623020801.GA156@afflictions.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040623020801.GA156@afflictions.org> X-Operating-System: FreeBSD 5.2-CURRENT on a i386 X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.6i Subject: Re: ipf 3.4.35 woes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 15:57:07 -0000 Thus spake Damian Gerow (dgerow@afflictions.org) [22/06/04 22:10]: : The upgrade to ipf 3.4.35 is causing me grief. And yes, my kernel and : userland are in sync: As someone pointed out to me, this is before the pf import -- these sources are from the eve of the ipf import, just after the two fixes were committed. I can completely and totally reproduce this on every reboot, but for the life of me, I can't reproduce it manually. It /appears/ to be either a problem with bringing up lo0, or a problem bringing up fxp0 with dhclient. Or something that might happen between those two steps, I'm not sure. - Damian