From owner-freebsd-stable@FreeBSD.ORG Mon May 8 10:32:13 2006 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 445EA16A4E1 for ; Mon, 8 May 2006 10:32:13 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99B7F43D45 for ; Mon, 8 May 2006 10:32:12 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.6/8.13.6) with ESMTP id k48AWAlA096942; Mon, 8 May 2006 14:32:10 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Mon, 8 May 2006 14:32:10 +0400 (MSD) From: Dmitry Morozovsky To: Iantcho Vassilev In-Reply-To: <18e02bd30605080206x3c3c908blbcb1019f146d22da@mail.gmail.com> Message-ID: <20060508143014.Q40914@woozle.rinet.ru> References: <20060508084807.GA16470@lpthe.jussieu.fr> <18e02bd30605080206x3c3c908blbcb1019f146d22da@mail.gmail.com> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Mon, 08 May 2006 14:32:11 +0400 (MSD) Cc: freebsd-stable@freebsd.org Subject: Re: pf not loading the rules at boot 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: Mon, 08 May 2006 10:32:13 -0000 On Mon, 8 May 2006, Iantcho Vassilev wrote: IV> > By the way, if you have a kernel *without* IPV6 support, the firewall IV> > module IV> > will *not* load. You will have to recompile the firewall module without IV> > IPV6 support first. This is the most common cause of the problem you are IV> > seeing. IV> IV> Thank you,Michel..,but it will not load on boot or? Neither, as it tries to refer to inet6 symbols; you have to build ipfw module with NO_INET6=yes too IV> If this is true maybe this is the problem - i have disabled IPV6 in the IV> kernel... Check `dmesg -a' output BTW, ipfw says ipfw2 (+ipv6) even when it is build without inet6, which is a bit misleading. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------