All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Schulman <andrex-cmaem7PIVQQM4YKboWzA4l6hYfS7NtTn@public.gmane.org>
To: netfilter-wool9L35kiczKOhml7GhPkB+6BGkLq7r@public.gmane.org
Subject: Re: Making a Bridging firewall
Date: Mon, 12 Apr 2004 13:47:04 -0400	[thread overview]
Message-ID: <MPG.1ae4a01fed9fd6ad9896aa@localhost> (raw)
In-Reply-To: 407AD23A.3030905@leaplab.com

> 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?

I found "Linux Firewalls", 2nd ed., by Robert Ziegler, to be an 
excellent, complete guide to packet filter firewalls in general, and 
iptables in particular.  None of it is specific to kernel 2.4, as far as 
I'm aware.  After reading it I built my firewall with kernel 2.4, and it 
continues to work just fine in kernel 2.6.

I'm not familiar with the bridge-nf patch, but you might be able to 
implement your bridge using just the FORWARD table.

Good luck,
Andrew. 

-- 
To reply by email, replace "deadspam.com" by "alumni.utexas.net"



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

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

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=MPG.1ae4a01fed9fd6ad9896aa@localhost \
    --to=andrex-cmaem7pivqqm4ykbowza4l6hyfs7nttn@public.gmane.org \
    --cc=netfilter-wool9L35kiczKOhml7GhPkB+6BGkLq7r@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.