From owner-freebsd-net@FreeBSD.ORG Mon Nov 17 09:07:53 2014 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1357C193 for ; Mon, 17 Nov 2014 09:07:53 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 674F8770 for ; Mon, 17 Nov 2014 09:07:51 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id sAH97gxH065980; Mon, 17 Nov 2014 20:07:42 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 17 Nov 2014 20:07:42 +1100 (EST) From: Ian Smith To: Sato Kentney Subject: Re: dragonflybsd's ipfw In-Reply-To: Message-ID: <20141117193354.T31139@sola.nimnet.asn.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2014 09:07:53 -0000 On Mon, 17 Nov 2014 15:48:13 +0800, Sato Kentney wrote: > I saw a email in dragonflybsd email list, someone is doing this! > http://www.dragonflybsd.org/docs/ipfw2/ We've had 'ipfw2' for a very long while. I couldn't help wondering why DF wouldn't just import our many years of development and experience rather than using bycn82's 'rewrite'? .. but DF already has ipfw2: http://leaf.dragonflybsd.org/cgi/web-man?command=ipfw§ion=ANY man page dated October 2008. Before tables, in-kernel NAT, later dummynet updates and no doubt more. So why not start from there? cheers, Ian