From owner-freebsd-security@FreeBSD.ORG  Mon Jun 23 15:47:06 2003
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1D78237B401
	for <FreeBSD-Security@FreeBSD.org>;
	Mon, 23 Jun 2003 15:47:06 -0700 (PDT)
Received: from mail.secureworks.net (mail.secureworks.net [209.101.212.155])
	by mx1.FreeBSD.org (Postfix) with SMTP id 3589943FAF
	for <FreeBSD-Security@FreeBSD.org>;
	Mon, 23 Jun 2003 15:47:05 -0700 (PDT)
	(envelope-from mdg@secureworks.net)
Received: (qmail 34210 invoked from network); 23 Jun 2003 22:44:11 -0000
Received: from unknown (HELO HOST-192-168-17-31.internal.secureworks.net)
	(63.239.86.253)
	by mail.secureworks.net with SMTP; 23 Jun 2003 22:44:11 -0000
Date: Mon, 23 Jun 2003 18:47:04 -0400 (EDT)
From: Matthew George <mdg@secureworks.net>
X-X-Sender: mdg@localhost
To: Michael Collette <metrol@metrol.net>
In-Reply-To: <200306201219.14573.metrol@metrol.net>
Message-ID: <20030623184332.U13040@localhost>
References: <200306201219.14573.metrol@metrol.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: FreeBSD Security <FreeBSD-Security@FreeBSD.org>
Subject: Re: IPFW: combining "divert natd" with "keep-state"
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Security issues [members-only posting]
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2003 22:47:06 -0000


On Fri, 20 Jun 2003, Michael Collette wrote:

> BTW, is there a way to give certain IPs permissions to reloading IPFW's
> rules?
> There's some stuff I'd like to be able to admin remotely.  Darn box
> won't let
> me reload rules, but it will let me reboot.  I've done this quite a bit
> in
> the past to force new rules to load.  I was rather hoping there was a
> more
> elegant solution to this.
>
> Later on,
>

if you have 'flush' at the top of your ruleset, you can (sometimes) get
away with an `ipfw -q`.  I find screen windows (ports/misc/screen) to be
most effective, though ... even if the connection dies, the screen will
detach and continue processing the rules file.

-- 
Matthew George
SecureWorks Technical Operations