From: Inaky Perez-Gonzalez <inaky@linux.intel.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>,
netdev@vger.kernel.org
Subject: Re: What makes a good fake MAC address?
Date: Wed, 22 Apr 2009 15:38:10 -0700 [thread overview]
Message-ID: <200904221538.10964.inaky@linux.intel.com> (raw)
In-Reply-To: <20090422152539.7a7e073a@s6510>
On Wednesday 22 April 2009, Stephen Hemminger wrote:
> On Wed, 22 Apr 2009 15:15:05 -0700
>
> Inaky Perez-Gonzalez <inaky@linux.intel.com> wrote:
> > On Wednesday 22 April 2009, Mark Smith wrote:
> > > Hi Inaky,
> > >
> > > (please CC me, I'm not on the list)
> > >
> > > "The problem with using a zero mac address is that it confuses the
> > > bridging software (and maybe others). I was wondering, what would
> > > be a fake mac address we could put in there that is legal for this
> > > kind of "faking"? [or the closest thing to legal?]"
> > >
> > > Since you're from an organisation with an OUI allocation or two, I
> > > think a real Intel one would be best. It then wouldn't be fake, and
> > > no matter where it was exposed (host only, local network, or
> > > globally e.g. in IPv6 node addresses), it would be guaranteed not
> > > to collide with any other addresses (unless Intel make error an
> > > error in their own OUI administration.)
> >
> > It doesn't really work, because it is for the "from" end of the
> > connection; as said somewhere else in the thread, the WiMAX link is
> > P2P, IP only. The card has a local address, that we use for the "to"
> > field, but for the from, we need to fake an address from the network
> > -- which is not necessarily an intel device :)
> >
> > So maybe local addresses would not be the right choice, and clearly
> > Intel assigned ones neither :)
>
> You need a from address for the bridge to be able to populate its
> forwarding table. If remote end is always same, just get some random
> address at start of tunnel and reuse it.
Nope, the remote end will change as you move around from base station to base
station :(
--
Inaky
next prev parent reply other threads:[~2009-04-22 22:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 21:34 What makes a good fake MAC address? Mark Smith
2009-04-22 22:15 ` Inaky Perez-Gonzalez
2009-04-22 22:25 ` Stephen Hemminger
2009-04-22 22:38 ` Inaky Perez-Gonzalez [this message]
2009-04-22 22:59 ` Stephen Hemminger
2009-04-22 23:35 ` Inaky Perez-Gonzalez
-- strict thread matches above, loose matches on Subject: below --
2009-04-22 20:48 Inaky Perez-Gonzalez
2009-04-22 21:13 ` Stephen Hemminger
2009-04-22 21:13 ` Eric Dumazet
2009-04-22 21:28 ` Inaky Perez-Gonzalez
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=200904221538.10964.inaky@linux.intel.com \
--to=inaky@linux.intel.com \
--cc=ipng@69706e6720323030352d30312d31340a.nosense.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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;
as well as URLs for NNTP newsgroup(s).