From owner-freebsd-bugs  Wed Apr  9 21:00:04 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA11587
          for bugs-outgoing; Wed, 9 Apr 1997 21:00:04 -0700 (PDT)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA11557;
          Wed, 9 Apr 1997 21:00:02 -0700 (PDT)
Date: Wed, 9 Apr 1997 21:00:02 -0700 (PDT)
Message-Id: <199704100400.VAA11557@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Adrian Chadd <adrian@obiwan.aceonline.com.au>
Subject: Re: kern/3244: ipfw flush closes connections
Reply-To: Adrian Chadd <adrian@obiwan.aceonline.com.au>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/3244; it has been noted by GNATS.

From: Adrian Chadd <adrian@obiwan.aceonline.com.au>
To: Adam David <adam@veda.is>
Cc: FreeBSD-gnats-submit@freebsd.org,
        GNATS Management <gnats@freefall.freebsd.org>,
        freebsd-bugs@freefall.freebsd.org
Subject: Re: kern/3244: ipfw flush closes connections
Date: Thu, 10 Apr 1997 11:45:12 +0800 (WST)

 On Thu, 10 Apr 1997, Adam David wrote:
 
 > 	When ipfw is used to flush previously established rules, (it seems)
 >         all tcp connections open at the time become closed. Since flush is
 > 	typical at the beginning of ipfw scripts and applies to rules not
 > 	connections, this behaviour is wrong. Several months ago, it was
 > 	possible to circumvent it (at least in part) by running /sbin/ipfw
 > 	as a background process, but no longer.
 >
 
 Huh?
  
 > >How-To-Repeat:
 > 
 > 	sh /etc/rc.firewall
 
 Try sh /etc/rc.firewall &
 
 I've noticed the same, if you do it remotely try sh /etc/rc.firewall &
 (I'm running a recentish build of 3.0-CURRENT and open tcp connections
 stay open).
 
 -- 
 Adrian Chadd			| UNIX, MS-DOS and Windows ...
 <adrian@psinet.net.au>		| (also known as the Good, the bad and the
 				|				ugly..)