From owner-freebsd-questions@FreeBSD.ORG  Fri Feb 27 11:40:14 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 69DE316A4CE
	for <freebsd-questions@freebsd.org>;
	Fri, 27 Feb 2004 11:40:14 -0800 (PST)
Received: from spock.ste-land.com (spock.ste-land.com [64.32.179.40])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1758A43D39
	for <freebsd-questions@freebsd.org>;
	Fri, 27 Feb 2004 11:40:12 -0800 (PST)
	(envelope-from ste@ste-land.com)
Received: from ste-land.com (bgp377940bgs.plnfld01.nj.comcast.net
	[68.36.5.198])
	by spock.ste-land.com (Postfix) with ESMTP id 40DCF2D24C
	for <freebsd-questions@freebsd.org>;
	Fri, 27 Feb 2004 14:40:11 -0500 (EST)
Message-ID: <403F9D1A.6020408@ste-land.com>
Date: Fri, 27 Feb 2004 14:40:10 -0500
From: "Shaun T. Erickson" <ste@ste-land.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4b) Gecko/20030507
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Firewall enabling confusion.
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2004 19:40:14 -0000

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

options		IPFIREWALL
options		IPFIREWALL_VERBOSE
options		IPFIREWALL_VERBOSE_LIMIT=100

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

	-ste