OpenThread Border Router logs explanation

Configuration Matter/Thread
1

Hello all-knowing forum,

Im currently trying to figure out Matter and bought a SkyConnect. I wanted to connect my Nuki Ultra with it, which worked (After enabling IPv6 Stack under Network in HomeAssistant).

It works well and very fast! NAT64 provides Internet Access to the Nuki and is reachable without normal Wifi :slight_smile:

Now more or less a problem I’m facing. The logs of the OpenThread Border Router constantly reports following message (level: notice):

00:15:02.547 [W] Nat64---------: no mapping found for the IPv4 address
00:15:40.067 [W] Nat64---------: no mapping found for the IPv4 address
00:16:52.005 [W] Nat64---------: no mapping found for the IPv4 address

Also those once at startup:

00:00:35.268 [W] DuaManager----: Failed to perform next registration: NotFound
00:00:38.991 [W] P-RadioSpinel-: Error processing result: NoAddress
00:00:38.991 [W] P-RadioSpinel-: Error waiting response: NoAddress

Full notice log since startup: https://pastebin.com/SRFAGNzc

Just wanted to ask if those errors are normal to appear so often?
Everything seems to work fine, so I’m wondering where they are coming from.

Thank you in advance!

Kind regards :slight_smile:

2

I don’t know about the Nat64 logs, but I did a quick scan of my logs and I don’t see those P-RadioSpinel logs. The RadioSpinel is essentially the communications between the OTBR Thread stack and the USB radio… but I don’t know what those errors mean.

3

Hey,

thanks for the response!

You do not get the RadioSpinel even on a fresh boot of the add-on? I could imagine that the sticks fw takes too long to flash and thats why I get this error on startup. I mean I only get it once, after it is fine.

Just the no mapping found error repeats. Could you maybe share your startup logs? Just so I know how a healthy Border Router looks like ^^

4

I guess it depends on what you mean by “fresh”. If you mean just a simple AddOn restart, no I don’t see the RadioSpinel error. If you mean while doing a reflash during a reboot because its doing a firmware upgrade, that I don’t know.

5

I get this message on every add-on restart.

Could the NAT64 info be from other multicaat packages in the network, which are dropped as there is not entry for them?

6

I’m not an expert on how the OTBR does NAT64, but the way I sorta think it works is that the OTBR maintains a dynamic mapping table with an entry that maps the device’s IPv6 address to a temporary IPv4 address that is used on the LAN/Ethernet side (the IPv4 address represents that Thread device). This IPv4 address has an expiration time (probably on the order of a few hours).

So my guess is that the OTBR is getting packets from the LAN side (possibly generated from the internet world) that is using one of these IPv4 addresses that has expired and thus there is no mapping entry for that address. It could be, that the OTBR restarted and thus wiped the mapping table clean, and gave the device a new/different IPv4 address, yet something is probably coming in on the LAN side is still trying to talk to the device using a stale IPv4.

7

I assume so too yes. But I can’t really figure out where the packages are coming from.
I removed the whole Matter Stack from HA again and started from scratch. Even with no devices and and a fresh installation the “error” appears constantly.

I also tried disabling mDNS repeater on my OPNsense to maybe block other Multicast traffic from different VLANs, which could behave weirdly with Thread. => Still happening.
Also a ZigBee network is running in parallel with a Sonoff Zigbee 3.0 USB Dongle Plus (CC2652P + CP2102(n)). ZIgbee Channel 15, Thread Channel 25.

Maybe here a debug log of the OTBR Add-on is helping? But I can’t really see any other indicators on what it could be.

Also here the normal logs while pairing the Nuki Lock again:

Pairing worked and the device showed up (Even with some errors in the logs).

8

If you (and/or your home router) have configured your LAN to use 192.168.255.0/24, then that may explain the mapping errors as this is also the network address the NAT64 wants to use for translation… otherwise I have no idea what is causing it.

9

Hey :slight_smile:
I’m not using this subnet. But I got a response from marcel on discord. (Discord)
He said that this error is perfectly normal and can be ignored.

So I’m not going to think about it any more.

Thanks for assisting me in this case :slight_smile: