Firewall enabling confusion.

Remko Lodder remko at
Fri Feb 27 11:44:16 PST 2004

kldstat is the program you are looking for (like lsmod)
It can indeed be that the module is loaded with it's default
settings {block all}

Hope this solves your lsmod question, the rest i cannot help you
with since i don't understand ipfw :) {yet}



Kind regards,

Remko Lodder Dutch community for helping newcomers on the
hackerscene Dutch mirror of MRTG

-----Oorspronkelijk bericht-----
Van: owner-freebsd-questions at
[mailto:owner-freebsd-questions at]Namens Shaun T. Erickson
Verzonden: vrijdag 27 februari 2004 20:40
Aan: freebsd-questions at
Onderwerp: Firewall enabling confusion.

I put 'firewall_enable="YES"' in /etc/rc.conf, in anticipation of
rebuilding my kernel with the following options turned on:


I rebooted, for unrelated reasons, and now see in the messages file that
ipfw2 has been enabled and, indeed, since I have no rules in place, my
system is cut off from the network.

I haven't yet rebuilt my kernel, so I don't understand why this kicked
in. Did adding that line in rc.conf suck in a kernel module that
obsoletes the need for those kernel options? How do I check (I'd do an
lsmod, on Linux - don't know what the equivalent FreeBSD command is)?
If it is a module, how do I enable logging, as adding
'firewall_logging="YES"' to /etc/rc.conf didn't turn it on, according to
the messages file. Likewise for divert (though I don't currently need it).

Feb 27 14:37:22 peter kernel: ipfw2 initialized, divert disabled,
rule-based forwarding enabled, default to deny, logging disabled


freebsd-questions at mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscribe at"

More information about the freebsd-questions mailing list