From chris@cheddar.netmonger.net  Thu May  1 09:41:39 1997
Received: from cheddar.netmonger.net ([165.254.145.62])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA01812
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 1 May 1997 09:41:36 -0700 (PDT)
Received: (from chris@localhost)
	by cheddar.netmonger.net (8.8.5/8.8.5) id MAA00330;
	Thu, 1 May 1997 12:41:22 -0400 (EDT)
Message-Id: <199705011641.MAA00330@cheddar.netmonger.net>
Date: Thu, 1 May 1997 12:41:22 -0400 (EDT)
From: chris@netmonger.net
Reply-To: chris@netmonger.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: rc.network calls rc.firewall incorrectly
X-Send-Pr-Version: 3.2

>Number:         3456
>Category:       conf
>Synopsis:       rc.network calls rc.firewall incorrectly
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu May  1 09:50:01 PDT 1997
>Closed-Date:    Thu May 1 13:04:58 PDT 1997
>Last-Modified:  Thu May  1 13:05:12 PDT 1997
>Originator:     Christopher Masto
>Release:        FreeBSD 2.2-STABLE i386
>Organization:
NetMonger Communications
>Environment:

	

>Description:

/etc/rc.network calls /etc/rc.firewall with "sh /etc/rc.firewall".  This
fails to propagate the "firewall" environment variable, which makes the
firewall always come up completely closed.

>How-To-Repeat:

Compile a kernel with IPFIREWALL, set firewall="open" in /etc/rc.conf,
and boot the system.

>Fix:
	
I think it should be ". /etc/rc.firewall".

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: jkh 
State-Changed-When: Thu May 1 13:04:58 PDT 1997 
State-Changed-Why:  
Done, thanks! 
>Unformatted:
