From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: iptables bridge filter question
Date: Thu, 18 Mar 2004 15:33:58 +0000 [thread overview]
Message-ID: <200403181533.58166.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <200403181524.35795.Antony@Soft-Solutions.co.uk>
On Thursday 18 March 2004 3:24 pm, Antony Stone wrote:
> On Thursday 18 March 2004 8:28 am, Gerry Weaver wrote:
> > Hello All,
> >
> > I have setup a bridging firewall. I want to drop packets on the external
> > interface, which have source addresses on my internal network. However,
> > the firewall/bridge sits between my T1 router and the rest of my LAN. Is
> > there a way to drop the packets mentioned previously, but allow the
> > router? I guess a rule could be created that uses the routers mac address
> > as a match. I've been playing around with this, but I'm not getting the
> > result I want. I could sure use some advice on this.
> >
> > [ LAN xx.xx.xx.0/24 ]<==>[ bridge/firewall ]<==>[ router xx.xx.xx.254/24
> > ]
>
> How about:
>
> iptables -A FORWARD -i $extIF -s xx.xx.xx.254 -j ACCEPT
> iptables -A FORWARD -i $extIF -s xx.xx.xx.0/24 -j DROP
Okay, scrub that - I overlooked the significance of it being a *bridging*
firewall :(
Antony.
--
All matter in the Universe can be placed into one of two categories:
1. Things which need to be fixed.
2. Things which need to be fixed once you've had a few minutes to play with
them.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-03-18 15:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 8:28 iptables bridge filter question Gerry Weaver
2004-03-18 15:24 ` Antony Stone
2004-03-18 15:33 ` Antony Stone [this message]
2004-03-18 19:28 ` Vincent Haverlant
2004-03-18 20:12 ` Gerry Weaver
2004-03-18 20:40 ` Antony Stone
2004-03-18 23:09 ` Gerry Weaver
2004-03-18 23:16 ` Antony Stone
-- strict thread matches above, loose matches on Subject: below --
2004-03-18 15:02 Steve Jones
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=200403181533.58166.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.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