RELENG_5 kernel b0rken with IPFIREWALL and without PFIL_HOOKS
barney at databus.com
Thu Aug 19 09:13:31 PDT 2004
On Thu, Aug 19, 2004 at 08:59:19AM -0700, David Wolfskill wrote:
> g1-15(5.2-C) uname -a
> FreeBSD g1-15.catwhisker.org 5.2-CURRENT FreeBSD 5.2-CURRENT #273: Wed Aug 18 15:55:18 PDT 2004 root at g1-15.catwhisker.org:/common/S2/obj/usr/src/sys/LAPTOP_30W i386
> g1-15(5.2-C) sudo ipfw list
> 00100 allow ip from any to any via lo0
> 00200 deny ip from any to 127.0.0.0/8
> 00300 deny ip from 127.0.0.0/8 to any
> 03200 deny log ip from any to any
> 65535 deny ip from any to any
> g1-15(5.2-C) kldstat
> Id Refs Address Size Name
> 1 7 0xc0400000 4b9ac4 kernel
> 2 14 0xc08ba000 536b0 acpi.ko
> 3 1 0xc1829000 17000 linux.ko
> Or am I missing your point?
> >Is it relevant that my /usr is on vinum, and the rules are in /usr/local/etc?
> Hmm... dunno. I'm not using vinum, and my rules are created via a shell
> script from a template on /etc (via dhcp-exit-hooks).
Sure, invoking ipfw directly works fine when ipfw's compiled into the kernel,
as does dotting /etc/rc.firewall. But /etc/rc.d/ipfw is what's run at
boot time, and that would seem, at least as I read it, to require that
ipfw be a module, not compiled in.
Barney Wolff http://www.databus.com/bwresume.pdf
I'm available by contract or FT, in the NYC metro area or via the 'Net.
More information about the freebsd-current