Date: Tue, 23 Sep 1997 08:03:55 +1000 (EST) From: "Daniel O'Callaghan" <danny@panda.hilink.com.au> To: Chris Stenton <jacs@gnome.co.uk> Cc: stable@FreeBSD.ORG Subject: Re: ipfw logging problem Message-ID: <Pine.BSF.3.91.970923075843.818m-100000@panda.hilink.com.au> In-Reply-To: <199709221642.RAA00380@hawk.gnome.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 22 Sep 1997, Chris Stenton wrote:
>
> I have recently performed a "make world" updated rc.conf etc and rebuilt my
> kernel. However, I have found that logging has stopped working. Looking at the
> message log I find that on bootup I get:-
>
> Sep 22 17:33:22 hawk /kernel: changing root device to sd0a
> Sep 22 17:33:22 hawk /kernel: IP packet filtering initialized, divert
> disabled, logging limited to 50 packets/entry
> Sep 22 17:33:22 hawk /kernel: IP packet filtering initialized, divert
> disabled, logging disabled
>
> Anyone know why I am getting two messages with the second disabling logging?
Sorry, mea culpa. When you say firewall="YES" in rc.conf, rc.network
will attempt to find the firewall code in kernel and if it is not there,
will load the lkm. My test was broken, so the LKM was loaded even if
firewalling was in the kernel.
I've fixed it in -stable now. Patch below.
regards,
Danny
--- rc.network.orig Thu Sep 18 15:48:31 1997
+++ rc.network Thu Sep 18 15:47:12 1997
@@ -58,7 +58,7 @@
# Initialize IP filtering using ipfw
echo ""
/sbin/ipfw -q flush > /dev/null 2>&1
- if [ $? ] ; then
+ if [ $? = 1 ] ; then
firewall_in_kernel=0
else
firewall_in_kernel=1
--- rc.firewall.orig Thu Sep 18 15:48:14 1997
+++ rc.firewall Thu Sep 18 15:47:10 1997
@@ -167,5 +167,5 @@
# Everything else is denied as default.
elif [ "${firewall_type}" != "NONE" -a -r "${firewall_type}" ]; then
- $fwcmd ${firewall}
+ $fwcmd ${firewall_type}
fi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.970923075843.818m-100000>