On 8/11/10, Mariano Alvira <[email protected]> wrote: > On Tue, Aug 10, 2010 at 05:08:16PM -0400, Jon Smirl wrote: >> On Tue, Aug 10, 2010 at 4:26 PM, Dmitry Eremin-Solenikov >> <[email protected]> wrote: >> > On 8/10/10, Jon Smirl <[email protected]> wrote: >> >> I'm added a command to the serial serial driver to retrieve the MAC >> >> address. That let me implement the code needed to auto-add link local >> >> addresses. >> >> >> >> wpan0 Link encap:IEEE 802.15.4 HWaddr 00:50:c2:ff:fe:a8:a8:c5 >> >> inet6 addr: fe80::50:c2ff:fea8:c545/64 Scope:Link >> > >> > This looks wrong. As hw-addr of WPAN device is 64-bit, IPv6 addr should >> > not contain fffe part. Or ff:ffe is a part of your real MAC address? >> >> ffee is part of the real MAC address. Mar owns a block of Ethernet >> addresses. To generate 64b addresses he added the ff:fe. >> >> Mar, are you sure that is right? If you shipped Ethernet devices using >> one of your addresses the kernel would convert them to have the ff:fe >> and they would conflict. It would make more sense to use anything but >> FF:FE. Or is the rule that if you use the 64b version you can't also >> distribute the 48b one? > > I followed this to encapsulate an EUI-48 in an EUI-64 > > http://standards.ieee.org/regauth/oui/tutorials/EUI64.html
Please refer to the part 'Restricted encapsulated values'. IMO you should have generated EUI-64 directly from OUI/extid EUI-48 -> EUI-64 is really meant for cases where manufacturer provides 48-bit address (like ethernet card), but we need 64-bit one (like in IPv6). -- With best wishes Dmitry ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Linux-zigbee-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
