Date: Thu, 19 Aug 2004 11:43:34 -0400 From: Barney Wolff <barney@databus.com> To: current@freebsd.org Subject: Re: RELENG_5 kernel b0rken with IPFIREWALL and without PFIL_HOOKS Message-ID: <20040819154334.GA23926@pit.databus.com> In-Reply-To: <200408191300.i7JD0wvm006811@the-macgregors.org> References: <41249DEA.80404@portaone.com> <200408191300.i7JD0wvm006811@the-macgregors.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I was inspired by the PFIL_HOOKS discussion to check my firewall rules :) There were none, other than 65535. Apparently, /etc/rc.d/ipfw attempts to kldload ipfw, which will fail if ipfw is compiled into the kernel, and since the precmd failed, the _cmd will not be run. When did it become mandatory to have ipfw as a module, not compiled in? Is there some rationale for this? It strikes me as rather dangerous, especially for firewalls, especially when default-to-accept is chosen. Am I just confused, and missing some obvious bit of config? Is it relevant that my /usr is on vinum, and the rules are in /usr/local/etc? Thanks, Barney
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040819154334.GA23926>