On Wed, Sep 8, 2010 at 11:43 AM, Jon Smirl <[email protected]> wrote: >> "For example, the Interface Identifier for an Ethernet interface whose >> built-in address is, in hexadecimal,
Interface Identifier != MAC address. It is a two step process. For Ethernet (48b) MAC addresses..... 34-56-78-9A-BC-DE First convert it to a 64b MAC address: 34-56-78-FF-FE-9A-BC-DE Now flip the universal/local bit 36-56-78-FF-FE-9A-BC-DE That's your link local address. ---------------------------------- For 802.15.4 (64b) MAC addresses..... 34-56-78-00-00-9A-BC-DE Anything except FFFE in the middle. FFFE is special key for 48/64 conversion Now flip the universal/local bit 36-56-78-00-00-9A-BC-DE That's your link local address. >> >> 34-56-78-9A-BC-DE >> >> would be >> >> 36-56-78-FF-FE-9A-BC-DE." >> >> >> From my understanding of this, the HW address will be the EUI64 and >> and the ipv6 address will have the FFFE in the middle. >> >> So for Redwire, we could have HW: 00-50-C2-A8-Cx-xx-yy-yy >> >> and the "Interface Identifier" would be (I supppose): >> >> 00-50-C2-FF-FE-A8-Cx-xx >> >> but which group of bits to put as "x-xx" doesn't seem properly defined >> (at least for IAB owners). It's also annoying that, I have 28 bits in >> my EUI64, but RFC4944 is saying I can only use 12, even though as you >> state 802.15.4 uses 64-bit addresses and so does ipv6 so why is >> RFC4944 making me go from 64-> 48 -> back to 64? >> >> Does anyone have any thoughts? >> >> -Mar. >> >> > > > > -- > Jon Smirl > [email protected] > -- Jon Smirl [email protected] ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Linux-zigbee-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
