From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.samba.org
Subject: Re: bridging with iptables (was no subject)
Date: Fri, 28 Jun 2002 23:29:48 +0100 [thread overview]
Message-ID: <20020628222950.JIAL295.mta03-svc.ntlworld.com@there> (raw)
In-Reply-To: <0GYF00FO1SU6ML@l-daemon>
On Friday 28 June 2002 11:22 pm, Jack Bowling wrote:
> Nothing to add. Just changed the subject line to something useful for the
> archives and search engines.
Good idea.
In which case.... can anyone here give some advice on combining netfilter
with a bridge (which, as Patrick kindly pointed out) doesn't have an IP
address on *either* (any?) of its interfaces ?
ie does the standard Linux routing system, and the various netfilter hooks,
still work sensibly enough to be able to put netfilter rules onto a bridge ?
Or is netfilter based so much around routing concepts and interfaces with
addresses on them that it doesn't really work properly ?
I'm sure I'll find a use for a bridge one day, so it'd be good to know
whether I can put netfilter on it when I do.
Antony.
> > On Friday 28 June 2002 9:02 pm, Patrick Schaaf wrote:
> > > Hi Antony,
> > >
> > > > Hmmm. I thought a bridge was supposed to have the same address on
> > > > both interfaces. Still, I've never set one up myself, so maybe
> > > > there's more than one way to do it.
> > >
> > > A bridge, by its nature, has no IP addresses at all. The original
> > > poster is asking about a pure router.
> >
> > Ugh. In that case I recommend using IPs from two *different* network
> > ranges on the two sides of the machine !
> >
> > > And you are right on spot with your observation about the ability of a
> > > malicious user to fake her MAC address at will. And one nice thing
> > > about most wireless networks is that I can just listen to the air for
> > > some time to learn what MAC/IP combination it is that I should fake
> > > after it became silent...
> >
> > Indeed. There may be anti-sniffing measures available for wired
> > networks, but I know of nothing which can detect / defeat sniffing on
> > wireless.
> >
> >
> >
> > Antony.
next prev parent reply other threads:[~2002-06-28 22:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000901c1000a$8aaa63e0$4d2848c7@shaggy>
2002-06-28 19:48 ` (no subject) Antony Stone
2002-06-28 20:02 ` Patrick Schaaf
2002-06-28 20:00 ` Antony Stone
2002-06-28 22:22 ` bridging with iptables (was no subject) Jack Bowling
2002-06-28 22:29 ` Antony Stone [this message]
2002-06-28 22:39 riffraff
2002-06-28 22:53 ` Antony Stone
2002-06-28 23:50 ` Martin Josefsson
2002-06-30 4:01 ` Joe Patterson
2002-06-30 7:13 ` Patrick Schaaf
2002-06-30 12:21 ` Martin Josefsson
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=20020628222950.JIAL295.mta03-svc.ntlworld.com@there \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.samba.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