Error UDP checksum

[Yasmine Safi]

Hello everyone, 

I am new to openthread and I have now a mesh network with a border router and other nodes. I have been facing the problem of error UDP checksum showing on the border router's logs.  All the nodes  joined the same network but this error still sometimes appears.

On the border router, I configured the network from the GUI and I have another end device running with openthread cli project from siliconlabs. 

I configured the masterkey on the other end device to join the existing network. 

it joined, but on the border router logs, that's what I see: 

Feb 16 11:03:58 beaglebone otbr-agent[1358]: [INFO]-MAC-----:     src:[fdb3:66f2:d407:1e8e:0:ff:fe00:bc2e]:61631

Feb 16 11:03:58 beaglebone otbr-agent[1358]: [INFO]-MAC-----:     dst:[fdb3:66f2:d407:1e8e:0:ff:fe00:bc00]:61631

Feb 16 11:03:58 beaglebone otbr-agent[1358]: [NOTE]-IP6-----: Error UDP Checksum

Feb 16 11:03:59 beaglebone otbr-agent[1358]: [NOTE]-IP6-----: Failed to handle payload: Drop

on the border router, I also sent a cli command ipaddr, and that's what I have:

fd22:22:0:0:ff41:b1d:8411:6bea

fdb3:66f2:d407:1e8e:0:ff:fe00:fc00

fdb3:66f2:d407:1e8e:0:ff:fe00:bc00

fdb3:66f2:d407:1e8e:2057:5ea2:709:b14

fe80:0:0:0:e891:c51b:e48c:f2f1

on the other node, I also sent a cli command ipaddr, and that's what I have: 

fd22:22:0:0:3978:c91a:c1d4:e95f

fdde:ad00:beef:0:0:ff:fe00:bc2e

fdde:ad00:beef:0:c512:3f8f:8796:521f

fe80:0:0:0:7c99:d001:dd05:664c

the border router is the leader with RLOC16 0xbc00 and the other node identifies itself as its child with rloc16 0xbc2e but it seems like they don't share the same mesh-local prefix (PS: both of them have the same active dataset).

Any suggestions/ideas on how to fix this? thank you I would really appreciate it :) 

[Jonathan Hui]

It appears that the Active Operational Dataset is not consistent between your devices. In particular, the mesh-local prefix is different (fdb3:66f2:d407:1e8e::/64 vs. fdde:ad00:beef:/64). This will cause 6LoWPAN compression to fail and, as a result, UDP checksum verification to fail.

You have two options when configuring the Active Operational Dataset:

Option 1: Follow the Quick Start section in src/cli/README_DATASET.md

Option 2: Set the entire Active Operational Dataset as hex-encoded data.

You can retrieve the complete Active Operational Dataset from the first node using:

dataset active -x
0e080000000000010000000300001035060004001fffe002084eb74ab03c56e6d00708fdc7fe165c83a67805108e2104f183e698da87e96efc1e45aa51030f4f70656e5468726561642d383631310102861104108d6273023d82c841eff0e68db86f35740c030000ff
Done

Then set it on another node using:

dataset set active 0e080000000000010000000300001035060004001fffe002084eb74ab03c56e6d00708fdc7fe165c83a67805108e2104f183e698da87e96efc1e45aa51030f4f70656e5468726561642d383631310102861104108d6273023d82c841eff0e68db86f35740c030000ff
Done

You can find more details in src/cli/README_DATASET.md.

Hope that helps.

--

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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/1c07c20e-f2cb-48c5-bd72-7d24a84c4bban%40googlegroups.com.