#OpenThread Border Router logs explanation

1 messages · Page 1 of 1 (latest)

raw glacier
#

Hello all-knowing discord,

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 🙂

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!

golden lodge
#

Perfectly normal, just ignore it.

raw glacier
#

Hey marcel :) Thanks for the reply and the relieve. I was about to turn crazy and tried to find an issue on my network. During the add of the nuki ultra, I got two new errors. (Everything still worked) I assume everything normal again and I should just ignore them? (At the end: https://pastebin.com/4dDsCPc9)

P.s. also opened thread in the forum so other people can find it more easily: https://community.home-assistant.io/t/openthread-border-router-logs-explanation/886375

golden lodge
#

The thread otbr addon is just very noisy and logs every blib. Take it with a grain of salt unless you see some really severe stuff being logged.

Better is to look at the matter server logging. That should be rather calm.
If that logs a lot of "chip timeouts" and whatnot, you have some serious issues going on at the (thread) network level.