OpenThread CoAP response is not transmitted

RE: OpenThread CoAP response is not transmitted

Tristen — Fri, 06 Jan 2023 14:40:02 GMT

I believe I found the issue and it is more related to the host Linux system's source IP address selection rules (I'm using Debian). By default, the system was using the wlan0 inet6 address as opposed to the wpan0 inet6 address (wpan0 is used by ot-daemon/RCP). I was able to fix this by changing the rules by setting the desired outgoing address as the home address. This causes the correct wpan0 inet6 address to win when the source selection rules are applied.

The command I used was ip addr change fdca:27f4:d1ed:a0fe:6b70:406d:1275:4eb8 home dev wpan0. This change is not persistent and will need to be set permanently.

RE: OpenThread CoAP response is not transmitted

Tristen — Fri, 06 Jan 2023 13:16:07 GMT

I'm deleting my old answer. Everything was working while I was on a work trip in a different environment. Now that I'm home, the setup is no longer working ,which makes me wonder if there is an environmental issue causing this. In either case, I'm still stuck and this project is once again blocked.

The environment during my work trip had no other 802.15.4 devices in the area. However, there are a number of 802.15.4 devices in my house (Google Home, etc.).

Now I'm wondering if there is something going on related to my home environment.

RE: OpenThread CoAP response is not transmitted

Tristen — Tue, 03 Jan 2023 16:15:13 GMT

non-working.pcapng: Response sent using the requesters peer address.
working.pcapng: Response sent using the multicast address.

devzone.nordicsemi.com/.../2335.non_2D00_working.pcapng
devzone.nordicsemi.com/.../1830.working.pcapng

RE: OpenThread CoAP response is not transmitted

Amanda Hsieh — Tue, 03 Jan 2023 16:08:34 GMT

Hi,

Please kindly provide a sniffer trace of the working and not working situations.

Regards,
Amanda H.