From owner-freebsd-net@FreeBSD.ORG Wed Feb 11 22:34:19 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55BB71065670 for ; Wed, 11 Feb 2009 22:34:19 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id DEC608FC19 for ; Wed, 11 Feb 2009 22:34:18 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id n1BMYHI9016382 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 11 Feb 2009 14:34:18 -0800 Received: from ptavv.es.net by postal1.es.net (Postal Node 1) with ESMTP (SSL) id SYT20817 for ; Wed, 11 Feb 2009 14:34:17 -0800 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 5550A1CC0B for ; Wed, 11 Feb 2009 14:34:16 -0800 (PST) To: freebsd-net@freebsd.org Date: Wed, 11 Feb 2009 14:34:16 -0800 From: "Kevin Oberman" Message-Id: <20090211223416.5550A1CC0B@ptavv.es.net> X-SPF-Result: pass X-SPF-Record: v=spf1 mx a:mail1.es.net a:mail2.es.net a:mail3.es.net a:mail4.es.net a:mail.es.net a:mailgw.es.net a:postal1.es.net a:postal2.es.net a:postal3.es.net ~all X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.7400:2.4.4, 1.2.40, 4.0.166 definitions=2009-02-11_10:2009-02-10, 2009-02-11, 2009-02-11 signatures=0 Subject: Support for IPv6 tables in ipfw? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2009 22:34:19 -0000 With all of Luigi's excellent work on ipfw, I'd like to request that someone familiar with the code look at implementing support for tables for IPv6. While the IPv6 support in IPFW is generally a bit less mature than IPv4, the one functional thing that is completely missing is tables. Having them would make my life quite a bit easier. It's the one thing that I have been unable to work around in my dual-stack firewalls. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751