From: Inaky Perez-Gonzalez <inaky@linux.intel.com>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: netdev@vger.kernel.org
Subject: Re: What makes a good fake MAC address?
Date: Wed, 22 Apr 2009 14:28:03 -0700 [thread overview]
Message-ID: <200904221428.03539.inaky@linux.intel.com> (raw)
In-Reply-To: <49EF8891.9010306@cosmosbay.com>
On Wednesday 22 April 2009, Eric Dumazet wrote:
> Inaky Perez-Gonzalez a écrit :
> > Hi All
> >
> > The Intel i2400m WiMAX driver behaves as an ethernet device, and
> > currently when sending packets to the netdev stack, it fakes an ethernet
> > header, sets the "from" mac address to zeroes and the "to" to it's own
> > MAC address.
> >
> > The WiMAX network can be considered to be a point-to-point (up to the
> > gateway) connection, all IP based, so there are not MAC addresses from
> > our gateway (not to mention that it can change behind us).
> >
> > 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?]
> >
> > Thanks!
>
> We have random_ether_addr(), it should be self explained :)
(Also in reply to Stephen's comment) the device has its own local address;
what we are faking is the address the packet comes from.
According to random_ether_addr(), it sets the local bits; will this work to
fake the "other end of the connection"? (for which there is an IP address but
no MAC address, it being a pure IP link).
Thanks,
--
Inaky
next prev parent reply other threads:[~2009-04-22 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 20:48 What makes a good fake MAC address? 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-22 21:34 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
2009-04-22 22:59 ` Stephen Hemminger
2009-04-22 23:35 ` 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=200904221428.03539.inaky@linux.intel.com \
--to=inaky@linux.intel.com \
--cc=dada1@cosmosbay.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).