From: Stefan Schmidt <stefan@osg.samsung.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>,
Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCH,RFC bluetooth-next 1/2] ieee802154: Fix generation of random EUI-64 addresses.
Date: Fri, 29 May 2015 10:21:35 +0200 [thread overview]
Message-ID: <5568218F.3070108@osg.samsung.com> (raw)
In-Reply-To: <20150529031958.GL11340@wantstofly.org>
Hello.
On 29/05/15 05:19, Lennert Buytenhek wrote:
> On Thu, May 28, 2015 at 04:42:53PM +0200, Alexander Aring wrote:
>
>
>> I am currently really unsure and looking in well-known IoT OS, if they
>> look on this bit. But I didn't saw anything. Only that the most using
>> the same like eth_random_addr address and fill with ff fe bit pattern.
>> Maybe to operate with some virtual linux networking ethernet interfaces
>> which are connected over slip and tun/tap and such things...
> ff fe bit pattern?
What they do is mapping a EUI-48 to a EUI-64 following the guidelines from:
https://standards.ieee.org/develop/regauth/tut/eui48.pdf page 4
The two missing octets are filled in with either FF FE or FF FF. The
padding happens after the first three bytes with the OUI and the rest of
the EUI-48.
regards
Stefan Schmidt
next prev parent reply other threads:[~2015-05-29 8:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 12:38 [PATCH,RFC bluetooth-next 1/2] ieee802154: Fix generation of random EUI-64 addresses Lennert Buytenhek
2015-05-28 13:17 ` Alexander Aring
2015-05-28 13:39 ` Lennert Buytenhek
2015-05-28 14:12 ` Lennert Buytenhek
2015-05-28 14:42 ` Alexander Aring
2015-05-28 14:53 ` Alexander Aring
2015-05-29 3:22 ` Lennert Buytenhek
2015-05-29 3:19 ` Lennert Buytenhek
2015-05-29 8:21 ` Stefan Schmidt [this message]
2015-05-29 8:27 ` Lennert Buytenhek
2015-05-28 15:13 ` Phoebe Buckheister
2015-05-28 15:23 ` Alexander Aring
2015-05-28 16:11 ` Marcel Holtmann
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=5568218F.3070108@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=alex.aring@gmail.com \
--cc=buytenh@wantstofly.org \
--cc=linux-wpan@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