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 [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
