From owner-freebsd-bugs Wed Apr 9 20:57:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA11383 for bugs-outgoing; Wed, 9 Apr 1997 20:57:21 -0700 (PDT) Received: from obiwan.aceonline.com.au (obiwan.aceonline.com.au [203.103.90.67]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA11336; Wed, 9 Apr 1997 20:56:39 -0700 (PDT) Received: from localhost (adrian@localhost) by obiwan.aceonline.com.au (8.8.5/8.8.5) with SMTP id LAA02204; Thu, 10 Apr 1997 11:45:13 +0800 (WST) Date: Thu, 10 Apr 1997 11:45:12 +0800 (WST) From: Adrian Chadd To: Adam David cc: FreeBSD-gnats-submit@freebsd.org, GNATS Management , freebsd-bugs@freefall.freebsd.org Subject: Re: kern/3244: ipfw flush closes connections In-Reply-To: <199704100152.BAA08167@veda.is> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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 ... | (also known as the Good, the bad and the | ugly..)