From owner-freebsd-questions@FreeBSD.ORG  Thu Jan 12 21:23:26 2006
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: 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 BF8E816A41F
	for <freebsd-questions@freebsd.org>;
	Thu, 12 Jan 2006 21:23:26 +0000 (GMT)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6149F43D45
	for <freebsd-questions@freebsd.org>;
	Thu, 12 Jan 2006 21:23:26 +0000 (GMT)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1])
	by dc.cis.okstate.edu (8.12.6/8.12.6) with ESMTP id k0CLNPhn001676
	for <freebsd-questions@freebsd.org>;
	Thu, 12 Jan 2006 15:23:25 -0600 (CST)
	(envelope-from martin@dc.cis.okstate.edu)
Message-Id: <200601122123.k0CLNPhn001676@dc.cis.okstate.edu>
To: freebsd-questions@freebsd.org
Date: Thu, 12 Jan 2006 15:23:25 -0600
From: Martin McCormick <martin@dc.cis.okstate.edu>
Subject: Re: Strange Failure Mode in FreeBSD 4.11 
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
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: Thu, 12 Jan 2006 21:23:26 -0000

Greg Barniskis writes:
>This section of rc.firewall refers to valid values you can place in 
>rc.conf for firewall_type. In rc.conf you can name any of the types 
>defined in rc.firewall /or/ you can specify a file of your own 
>(instead of rc.firewall). I don't think you can invoke rc.firewall 
>/and/ another file you name.

	That clears things up greatly!  Thank you.  I'll just make a
new file that combines rc.firewall and the extra rules I had and
reference that from rc.conf.local.  Again, many thanks.