From owner-freebsd-stable@FreeBSD.ORG Wed Dec 28 16:49:16 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96B4116A41F for ; Wed, 28 Dec 2005 16:49:16 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from skippyii.compar.com (test.compar.com [216.208.38.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id A20F643D58 for ; Wed, 28 Dec 2005 16:49:15 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (CPE00062566c7bb-CM0011e6ede298.cpe.net.cable.rogers.com [70.28.254.189]) by skippyii.compar.com (8.13.1/8.13.1) with ESMTP id jBSGoZPj054764; Wed, 28 Dec 2005 11:50:36 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <003301c60bce$c27a95e0$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: "Brian Candler" , References: <20051228155041.GA7124@uk.tiscali.com> Date: Wed, 28 Dec 2005 11:50:06 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Cc: Subject: Re: Strange problem with kldload and pf X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2005 16:49:16 -0000 > Fresh install of FreeBSD 6.0-RELEASE from CD. > > With the GENERIC kernel, I was able to 'kldload pf' to get the pf firewall. > However this doesn't work after I rebuilt a new kernel; it fails to load. > > All I did was add IPSEC and disable IPv6. The exact config diff from GENERIC > is attached below. > > However this module file definitely exists, and has a timestamp from when > the kernel was rebuilt: > > # ls -l /boot/kernel/pf.ko > -r-xr-xr-x 1 root wheel 188030 Dec 28 15:15 /boot/kernel/pf.ko > # wc -c /boot/kernel/pf.ko > 188030 /boot/kernel/pf.ko > > I guess I can go ahead and rebuild the kernel again, this time with pf built > in. However I would like to know why I can't load pf as a module, even > though it seems to have been successfully built as one. Sometimes kldload fails mysteriously, and more helpful error messages are dumped in /var/log/messages. But only sometimes. -- Matt Emmerton