From owner-freebsd-security Tue Oct 2 22:43:57 2001 Delivered-To: freebsd-security@freebsd.org Received: from mail.acns.ab.ca (h24-68-206-125.sbm.shawcable.net [24.68.206.125]) by hub.freebsd.org (Postfix) with ESMTP id C1D5E37B403 for ; Tue, 2 Oct 2001 22:43:52 -0700 (PDT) Received: from colnta.internal (colnta.internal [192.168.1.2]) by mail.acns.ab.ca (8.11.6/8.11.3) with ESMTP id f935ice01085 for ; Tue, 2 Oct 2001 23:44:38 -0600 (MDT) (envelope-from davidc@colnta.internal) Received: (from davidc@localhost) by colnta.internal (8.11.6/8.11.3) id f935icU94925 for freebsd-security@freebsd.org; Tue, 2 Oct 2001 23:44:38 -0600 (MDT) (envelope-from davidc) Date: Tue, 2 Oct 2001 23:44:38 -0600 From: Chad David To: freebsd-security@freebsd.org Subject: new ipfw command Message-ID: <20011002234438.A94897@colnta.internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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 I have started writing a new ipfw command (fwadm) that is much like ipfw, but differs in a number of areas: 1) I use lex and yacc to support a more flexable grammar. 2) I support command line, file, and interactive modes. (the interactive mode uses readline) 3) I've started an interactive help mode.. I'm thinking about modeling it after the Cisco IOS. 4) The code is modular enough to be useful to someone who didn't write it. What I am looking for are ideas, and before I put too much effort into this, an opinion on whether or not a more "friendly" ipfw is even a good idea. I have a number of my own ideas, but "usefulness" is my primary goal. Any comments or requests for the code in its current state are welcome. -- Chad David davidc@acns.ab.ca ACNS Inc. Calgary, Alberta Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message