Interoperability between devices running on OpenThread vs mbed Thread stacks

[Shahabuddin Mohammed]

Hi,

I have tried creating a Thread network using mbed Border Router and OpenThread based device.

FYI, I have used Border Router, created Thread network using another mbed device.
Devices running on OpenThread can create a Thread network without issues.

Issue is only when one device runs on mbed Thread stack, while other runs on OpenThread.
Neither of the two respond to the advertisement received.

If both the stacks conform to Thread specification, this should work!
Can someone please point what is wrong here?

As per my understanding none of the stacks do commissioning.

PS:There are in same channel with same panid.

Attached raw data packet from openthread device and mbed border router.

Thanks,
Shahab

[Jonathan Hui]

Hi Shahab,

On Wed, Aug 17, 2016 at 4:10 AM, Shahabuddin Mohammed <shahabud...@gmail.com> wrote:

I have tried creating a Thread network using mbed Border Router and OpenThread based device.

FYI, I have used Border Router, created Thread network using another mbed device.
Devices running on OpenThread can create a Thread network without issues.

Issue is only when one device runs on mbed Thread stack, while other runs on OpenThread.
Neither of the two respond to the advertisement received.

If both the stacks conform to Thread specification, this should work!
Can someone please point what is wrong here?

Interoperability is certainly the primary goal of an industry standard.  However, the Thread Certification program is currently under development and there are no existing Thread stacks that have been fully vetted against the Thread specification.  It does not surprise me that OpenThread and mbed Thread do not interoperate yet.

As per my understanding none of the stacks do commissioning.

Thread Commissioning support is currently under development in OpenThread and you can view its progress at PR #399.

PS:There are in same channel with same panid.

Attached raw data packet from openthread device and mbed border router.

Thanks.  It would be helpful if you could provide these in pcap format for easy viewing in wireshark.

--
Jonathan Hui

[Shahabuddin Mohammed]

Hi Jonathan,

Thank you for the prompt reply.

Please find the attached sniffer capture in pcap format.

The device running on OpenThread stack has MAC address,

 00:23:A7:FF:FF:08:9D:91

While the other device with mbed Thread stack has MAC address as,

E6:41:C9:E8:E4:67:F7:7E

Thanks,
Shahab

[Jonathan Hui]

Hi Shahab,

You did not indicate what Thread Master Key you were using.  As a result, I could not decrypt your packets.  I tried using the default Thread Master Key for OpenThread, but that did not work.

--

Jonathan Hui

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/10fdb0ee-6b45-4957-81d6-e15bbd9b9820%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Shahabuddin Mohammed]

Hi Johnathan,

I am indeed using the default master_key (0x00, 0x11, 0x22, ... 0xff).
Verified that the same master key is used by mbed Thread stack as well.

Thanks,
Shahab

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To post to this group, send email to openthre...@googlegroups.com.

[Jonathan Hui]

Wireshark fails to decrypt the MLE messages with the IEEE 802.15.4 Decryption Key preference set to: 00112233445566778899aabbccddeeff.

--
Jonathan Hui

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/7a355db4-d2ef-446a-ad30-2aff1ac48d6f%40googlegroups.com.

[Shahabuddin Mohammed]

On the CLI (using UART), I get masterkey as 00112233445566778899aabbccddeeff.
I am not sure why decryption fails.
 
Thanks,
Shahab

[Jonathan Hui]

Digging further, it looks like the UDP checksums in your trace are invalid for all of the MLE messages.

--

Jonathan Hui

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/69d4dc6a-ea17-4ada-aeb1-b4449f84494c%40googlegroups.com.

[Shahabuddin Mohammed]

Hi Jonathan,

I am sorry, I forgot to mention that the sniffer used is TI's CC2531 based dongle, which saves capture in .psd format.
I have used a script to convert it to pcap format, eventually FCS is lost.

Except packet #15 in the capture all others have correct FCS.

Thanks,
Shahab

[Jonathan Hui]

It seems that your conversion to pcap is not complete since the UDP checksum validation in wireshark fails on all IPv6 packets.  If you open your pcap file in wireshark and enable "Validate the UDP checksum if possible" preference, you should see the validation failures.

--

Jonathan Hui

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/9c2da454-0c62-4691-8860-3dcb23813cfe%40googlegroups.com.

[Shahabuddin Mohammed]

Yes, you are right!
I will verify the conversion and report.

Thanks,
Shahab

[Shahabuddin Mohammed]

Hi Jonathan,

I have captured the packet exchange with Freescale Thread sniffer dongle, please find the attached capture file in .pcap (zipped) format.
FYI, the network parameters are

NETWORK_NAME	Network000000000
MASTERKEY	00112233445566778899aabbccddeeff
EXTPANID	000db800004fbfa6
PANID	0xDEFA
MBED Thread Dev	92:7d:55:84:50:63:43:da
OT Thread Dev	ce:94:a9:30:63:f7:be:5d

I used another Thread node to send a Beacon Request (#12), responses from both the devices can be seen as #13, #14 in the capture.

The two devices don't join to form a single network.

Thanks,
Shahab

[Shahabuddin Mohammed]

Hi,

It works!!!

OpenThread device connects with an mbed Thread Border Router.
Attached a sniffer capture for the same.

Thanks,
Shahab

[Jonathan Hui]

Hi Shahab,

Great news!  Thanks for the update.  What was the root cause of the problem in your previous email?

--

Jonathan Hui

To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/cc4b971b-ca9a-4672-a139-2acb1c76d651%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

<Thread_mbed_717_vs_ot_5476.pcapng.zip>

[Shahabuddin Mohammed]

Hi Jonathan,

I simply upgraded mbed Thread Border Router image to latest one, this image is based on the latest mbed OS.
Earlier I was using an older version of mbed BR image.

Although, I still need to explore the changes done on their side.

Thanks,
Shahab