From owner-freebsd-questions Wed Sep 15 1:47:36 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mail.polytechnic.edu.na (mail.polytechnic.edu.na [196.31.225.2]) by hub.freebsd.org (Postfix) with ESMTP id ACA4814BD7; Wed, 15 Sep 1999 01:47:27 -0700 (PDT) (envelope-from tim@iafrica.com.na) Received: from [196.31.225.199] (helo=310.priebe.alt.na) by mail.polytechnic.edu.na with smtp (Exim 3.02 #2) id 11RCeJ-00072R-00; Wed, 15 Sep 1999 08:50:51 -0200 From: Tim Priebe Reply-To: tim@iafrica.com.na To: Bryan Talbot , "Greg Quinlan" , Subject: Re: New rc.conf entry question. Date: Wed, 15 Sep 1999 13:33:53 +0200 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain Cc: References: <4.2.0.58.19990914122726.00a802e0@mail.elcjn1.sdca.home.com> MIME-Version: 1.0 Message-Id: <99091513391007.09401@310.priebe.alt.na> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Sep 1999, Bryan Talbot wrote: > I accomplished this by simply setting > firewall_type="/etc/firewall_rules.m4" and modifying the last little bit of > the /etc/rc.firewall to read ... > > elif [ "${firewall_type}" != "UNKNOWN" -a -r "${firewall_type}" ]; then > $fwcmd -p /usr/bin/m4 ${firewall_type} > fi > > > This puts all the custom firewall rules into one location that should never > be disturbed by an upgrade. I couldn't get around the need to modify the > rc.firewall file somewhat though to allow for the use of M4. I have done the same thing here, but have used a different filter, as the person that will have to maintain the rules does not know m4. Shold there be a firewall_options variable added? Tim. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message