From owner-freebsd-net@FreeBSD.ORG Tue Dec 14 05:33:08 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4057116A506; Tue, 14 Dec 2004 05:33:08 +0000 (GMT) Received: from mx01.bos.ma.towardex.com (mx01.bos.ma.towardex.com [65.124.16.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E4A943D31; Tue, 14 Dec 2004 05:33:08 +0000 (GMT) (envelope-from haesu@mx01.bos.ma.towardex.com) Received: by mx01.bos.ma.towardex.com (TowardEX ESMTP 3.0p11_DAKN, from userid 1001) id 89ED32F947; Tue, 14 Dec 2004 00:33:07 -0500 (EST) Date: Tue, 14 Dec 2004 00:33:07 -0500 From: James To: Gleb Smirnoff Message-ID: <20041214053307.GA97056@scylla.towardex.com> References: <20041213124051.GB32719@cell.sick.ru> <41BDABFB.E64C0A31@freebsd.org> <20041213184700.GA37107@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041213184700.GA37107@cell.sick.ru> User-Agent: Mutt/1.4.1i cc: net@freebsd.org Subject: Re: per-interface packet filters X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.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: Tue, 14 Dec 2004 05:33:08 -0000 I'm personally against modifying ipfw(4) for this purpose. It gets into the complexity of syntax and simply violates the initial simple model of the whole ipfw packet filter itself. I agree in that freebsd systems acting as routers need a more "efficient" or "better" engine by allowing per-interface firewall hooks, but we all know pfil_hooks api already provides this; and modifying ipfw for this is just a mess for a little gain. That said, the pfil_hooks already provides the ifp -- so why not just write a new firewall of your own that is totally separate from pf/ipfw? Please feel free to make it as compiled (like Crisco Turbo ACL) instead of linear rule by rule checks :) Just need to make it compatible to pfil_hooks api. While it is good to make freebsd more router-like, keeping things simple for systems acting as non-routing platforms for endusers is also equally important. -J -- James Jun TowardEX Technologies, Inc. Technical Lead Boston IPv4/IPv6 Web Hosting, Colocation and james@towardex.com Network design/consulting & configuration services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net