Re: [PATCH,RFC bluetooth-next 1/2] ieee802154: Fix generation of random EUI-64 addresses.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux