https://devzone.nordicsemi.com/f/nordic-q-a/16887/set-last-byte-of-eui-48-to-0x00This piece of code appears in all IoT SDK examples: eui48_t ipv6_medium_eui48; err_code = ipv6_medium_eui48_get(m_ipv6_medium.ipv6_medium_instance_id, &amp;ipv6_medium_eui48); ipv6_medium_eui48.identifier[EUI_48_SIZE - 1] = 0x00; err_code = ipv6_medium_eui48_seten-USTelligent Community 13Mon, 10 Oct 2016 12:06:30 GMThttps://devzone.nordicsemi.com/thread/64686?ContentTypeID=1Mon, 10 Oct 2016 12:06:30 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4b67a727-53b8-49e9-afd6-7fe429024cf3Petter Myhre<p>Please have a look at <a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.iotsdk.v0.9.0/iot_sdk_user_guides_ipv6_address_creation.html?cp=4_1_0_2_4">this</a>.</p> <p>The 6LoWPAN implementation on Linux requires the BLE address to be public.</p> <p>When the BLE address is public the 7th bit in the first byte in the IID should be 1, because it is globally unique.</p> <p>And for it to 1, it has to be 0 in the EUI-64, since it is flipped. Since it is 0 in EUI-64, it has to be 0 in the public BLE address.</p> <p>Instead of only setting the 7th bit of 6th byte in the public BLE address we set the whole byte to 0x00, to make it easier for you to figure out what the IPv6 addresses are.</p><div style="clear:both;"></div>