Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Dave Barnum <dave@leaplab.com>
To: netfilter@lists.netfilter.org
Subject: Making a Bridging firewall
Date: Mon, 12 Apr 2004 10:30:34 -0700	[thread overview]
Message-ID: <407AD23A.3030905@leaplab.com> (raw)

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?

Thanks



             reply	other threads:[~2004-04-12 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-12 17:30 Dave Barnum [this message]
2004-04-12 17:39 ` Making a Bridging firewall Tom Eastep
2004-04-12 17:47   ` Dave Barnum
2004-04-12 17:47 ` Andrew Schulman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=407AD23A.3030905@leaplab.com \
    --to=dave@leaplab.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox