From: Jack Bowling <jbinpg@shaw.ca>
To: netfilter@lists.samba.org
Subject: Re: bridging with iptables (was no subject)
Date: Fri, 28 Jun 2002 15:22:52 -0700 [thread overview]
Message-ID: <0GYF00FO1SU6ML@l-daemon> (raw)
In-Reply-To: <20020628200048.TETZ19225.mta07-svc.ntlworld.com@there>
Nothing to add. Just changed the subject line to something useful for the archives and search engines.
jb
** Reply to message from Antony Stone <Antony@Soft-Solutions.co.uk> on Fri, 28 Jun 2002 21:00:46 +0100
> 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:22 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 ` Jack Bowling [this message]
2002-06-28 22:29 ` bridging with iptables (was no subject) Antony Stone
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=0GYF00FO1SU6ML@l-daemon \
--to=jbinpg@shaw.ca \
--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 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.