From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Eastep Subject: Re: Making a Bridging firewall Date: Mon, 12 Apr 2004 10:39:53 -0700 Sender: netfilter-admin@lists.netfilter.org Message-ID: <407AD469.1000101@shorewall.net> References: <407AD23A.3030905@leaplab.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <407AD23A.3030905@leaplab.com> Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Dave Barnum Cc: netfilter@lists.netfilter.org Dave Barnum wrote: > Hello.. I've been wanting to rewrite my firewall for a little bit but > i'm not that familiar with iptables.. Up until now i've had a shorewall > based firewall that also did bridging between my gateway and a VPN > gateway over the internet (to link our houses.) I used the bridge-nf > patch on the 2.4 kernel to be able to manage the bridge traffic and > block certain broadcast packets (like DHCP) I've now upgraded to the > 2.6 kernel because i heard it may fix some other issues i was having but > now my bridge (DHCP blocking) rules no longer work... I'd like to get > rid of shorewall and write my own IPTables in the hopes that i could get > my ability to control the bridge back. Can anyone make any suggestions, > or point to a guide that does this with the 2.6 kernel? Shorewall 2.0.1 contains bridge/firewall support -- it works well with 2.6 kernels. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net