From owner-freebsd-security Tue Jun 11 18:29:10 2002 Delivered-To: freebsd-security@freebsd.org Received: from caligula.anu.edu.au (caligula.anu.edu.au [150.203.224.42]) by hub.freebsd.org (Postfix) with ESMTP id B9C4737B405 for ; Tue, 11 Jun 2002 18:29:05 -0700 (PDT) Received: (from avalon@localhost) by caligula.anu.edu.au (8.9.3/8.9.3) id LAA08555; Wed, 12 Jun 2002 11:29:02 +1000 (EST) From: Darren Reed Message-Id: <200206120129.LAA08555@caligula.anu.edu.au> Subject: Re: Testing firewall rules To: elf@glassfish.net (Michael Tang Helmeste) Date: Wed, 12 Jun 2002 11:29:02 +1000 (Australia/ACT) Cc: freebsd-security@FreeBSD.ORG In-Reply-To: <3CFE9EA7.9000809@glassfish.net> from "Michael Tang Helmeste" at Jun 05, 2002 04:28:39 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In some mail from Michael Tang Helmeste, sie said: > > I sent this earlier but it seems to have gotten lost in the mail... > > Is there any way to test firewall rules with example packets before you > implement them? Maybe like a mock-ipfw and packet injection tool or > something. Some type of network stack emulator that reads IPFW style > rules? I have some very large ipfw rulesets and its hard to step thru > each rule and check it against a packet, especially for when you want to > test all different types of services, in both directions, etc. Were you using ipf, you could use ipftest. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message