Date: Tue, 14 Sep 1999 12:33:04 -0700 From: Bryan Talbot <btalbot@ucsd.edu> To: "Greg Quinlan" <Greg.Quinlan@swlct.sthames.nhs.uk>, <freebsd-questions@FreeBSD.ORG> Cc: <stable@FreeBSD.ORG> Subject: Re: New rc.conf entry question. Message-ID: <4.2.0.58.19990914122726.00a802e0@mail.elcjn1.sdca.home.com> In-Reply-To: <002001befeb0$d919d2c0$5214010a@swlct.sthames.nhs.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
-Bryan
At 05:58 AM 9/14/99 , Greg Quinlan wrote:
>I have noticed that there is a new entry in the /etc/defaults/rc.conf
>"firewall_script=/etc/rc.firewall", would it be advisable to have the
>default location for the firewall script as "/etc/defaults/rc.firewall"
>rather than "/etc/rc.firewall." Some people who have already customized
>their "/etc/rc.firewall" script and will feel confident that it will not be
>overwritten by and upgrade. Those doing a fresh install we not be effected
>either. :)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.2.0.58.19990914122726.00a802e0>