From owner-freebsd-questions@FreeBSD.ORG Thu Jan 25 04:03:53 2007 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B71D216A401 for ; Thu, 25 Jan 2007 04:03:53 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.249]) by mx1.freebsd.org (Postfix) with ESMTP id 93E2F13C448 for ; Thu, 25 Jan 2007 04:03:51 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.102] (adsl-65-69-140-8.dsl.rcsntx.swbell.net [65.69.140.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTP id 8C27C114307 for ; Wed, 24 Jan 2007 21:56:43 -0600 (CST) Date: Wed, 24 Jan 2007 22:03:49 -0600 From: Paul Schmehl To: questions@freebsd.org Message-ID: <8A718FEA9B0B613B880B9AD1@paul-schmehls-powerbook59.local> In-Reply-To: <20070124161732.N55095@prime.gushi.org> References: <20070124152310.E82156@prime.gushi.org> <20070124161732.N55095@prime.gushi.org> X-Mailer: Mulberry/4.0.7b1 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========5F09169061B0C0E5DF86==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Problem with "ipfw flush" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 04:03:53 -0000 --==========5F09169061B0C0E5DF86========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On January 24, 2007 4:18:12 PM -0500 "Dan Mahoney, System Admin"=20 wrote: > > Well, I'm trying to be compliant with /etc/rc.firewall's expectations > for a rules file, which IS called with ipfw "rules.file" > Are you aware that you can run /etc/rc.d/ipfw restart? You'll get locked out of that ssh session, but you can start another one=20 immediately. (Assuming you didn't screw up your rules, of course.) Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========5F09169061B0C0E5DF86==========--