Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Gavin Hamill <gdh@acentral.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: A drop-in firewall
Date: Thu, 4 Sep 2003 11:01:13 +0100	[thread overview]
Message-ID: <200309041101.13462.gdh@acentral.co.uk> (raw)
In-Reply-To: <5.2.1.1.0.20030830201439.01072380@fluent2.pyramid.net>

lOn Sunday 31 August 2003 04:25, Stephen Satchell wrote:

> Desired solution:  "Drop" a Linux box between the Windows boxes and the
> rest of the internal network.  Use IPTABLES to ensure that the Windows
> boxes can't do anything nasty to the rest of the systems in the room,
> without impairing access to the rest of the Internet.

What you want to do is perfectly common and perfectly achievable... However, 
can I suggest an alternative route? 

Check out the Linux bridge-filter patch which allows you to apply iptables 
rules whilst running a machine as a bridge - i.e. your eth0 and eth1 become a 
single 'br0' for management purposes..

The joy of this is that you CAN literally just drop the box in between your 
LAN and WAN, and you need not change ANY default gateway settings on either 
the routers or the Windows boxes.

I've been using an old P233 as a bridge-firewall for a client LAN of 50 
machines with 2Mbps upstream bandwidth, and the thing never misses a beat, 
and loadavg is usually below 0.05 

http://ebtables.sf.net/

and specifically http://ebtables.sourceforge.net/download.html

Cheers,
Gavin.


      parent reply	other threads:[~2003-09-04 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-31  3:25 A drop-in firewall Stephen Satchell
2003-09-04  9:53 ` Ralf Spenneberg
2003-09-04  9:59 ` Arnt Karlsen
2003-09-04 10:01 ` Gavin Hamill [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=200309041101.13462.gdh@acentral.co.uk \
    --to=gdh@acentral.co.uk \
    --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