Nordic Border Router suddenly stopped working

RE: Nordic Border Router suddenly stopped working

Brian (Geek) — Fri, 30 Sep 2022 12:59:10 GMT

Currently it's started working fine.

RE: Nordic Border Router suddenly stopped working

Sigurd Hellesvik — Thu, 29 Sep 2022 14:02:35 GMT

Hi,

[quote user="Brian (Geek)"]How can I solve this issue of end device not able to receive packet information ?[/quote]

Can you provide a sniffer log for the thread network of this problem?

Regards,
Sigurd Hellesvik

RE: Nordic Border Router suddenly stopped working

Brian (Geek) — Tue, 27 Sep 2022 06:04:27 GMT

Logs from RPi:

I have four border router setup two at client side and two are currently with me and have been tested one by one.

But suddenly all the border routers are having the same issue as mentioned in the log screenshot from above. I have even tried setting the static iaid for the wpan0 interface, which solves the above conflict I guess but the main issue of MQTTSN Gateway INFO packet is not getting received at end device is not getting resolved.

The same issue arrives when I press button 1 of DK board for gateway discovery the GW_INFO packet is not being recieved by DK board even with default SDK example and default Thread Border Router image.

How can I solve this issue of end device not able to receive packet information ?

RE: Nordic Border Router suddenly stopped working

Sigurd Hellesvik — Mon, 26 Sep 2022 13:19:14 GMT

Hi,

To avoid misunderstandings:
Can you point to the parts of your logs where the error happens?

Regards,
Sigurd Hellesvik

RE: Nordic Border Router suddenly stopped working

Brian (Geek) — Mon, 26 Sep 2022 11:49:11 GMT

I am even not able to run simple mqttsn default publisher example with default border router gateway available for test.

The thread device is not able to get gateway info as previously mentioned.

Here are the logs from the device:

<info> app_timer: RTC: initialized.

<info> app: Thread version   : OPENTHREAD/20191113-00534-gc6a258e3; NRF52840; Apr  5 2020 21:53:43

<info> app: Network name     : OpenThread

<info> app: Thread interface has been enabled.

<info> app: 802.15.4 Channel : 11

<info> app: 802.15.4 PAN ID  : 0xABCD

<info> app: Radio mode       : rx-off-when-idle

<warning> app_timer: RTC instance already initialized.

<info> app: State changed! Flags: 0x0103D21D Current role: 1



<info> app: State changed! Flags: 0x009533B7 Current role: 2



<info> app: State changed! Flags: 0x00000001 Current role: 2



<info> app: MQTT-SN event: Gateway discovery procedure has finished.



<info> app: MQTT-SN event: Gateway discovery result: 0x3.

RE: Nordic Border Router suddenly stopped working

Brian (Geek) — Mon, 26 Sep 2022 07:25:35 GMT

How to get that log ?

RE: Nordic Border Router suddenly stopped working

Sigurd Hellesvik — Mon, 26 Sep 2022 07:23:37 GMT

Hi,

Can you point out how I can see this error from the attached log?

Do you have a log from the Thread device as well?

Regards,
Sigurd Hellesvik

RE: Nordic Border Router suddenly stopped working

Brian (Geek) — Sat, 24 Sep 2022 04:46:13 GMT

Hello as mentioned by you i have provided the static IAID to the wpan0 interface.

Below is my updated dhcpcd.conf file :

- As you can see i have assigne d wpan0 interface "10" value.

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
duid

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac hwaddr

# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
nohook wpa_supplicant

denyinterfaces nat*

noipv6rs

interface wpan0
iaid 10
nodhcp
nodhcp6


interface eth0
iaid 1
ipv6rs
ia_na 2
ia_pd 3/::/63 wpan0/1

interface wlan0
iaid 4
ipv6rs
ia_na 5
ia_pd 6/::/63 wpan0/1


static domain_name_server=8.8.8.8

Here is the update log from RPi the interface seems to be up now but still my thread devices attached to the network are unable to receive the MQTTSN GW Search response.

Logs :

Sep 24 10:08:26 OTBR named[476]: GEO-106FREE 20170512 Bu
Sep 24 10:08:26 OTBR named[476]: initializing GeoIP Country (IPv6) (type 12) DB
Sep 24 10:08:26 OTBR named[476]: GEO-106FREE 20170512 Bu
Sep 24 10:08:26 OTBR named[476]: GeoIP City (IPv4) (type 2) DB not available
Sep 24 10:08:26 OTBR named[476]: GeoIP City (IPv4) (type 6) DB not available
Sep 24 10:08:26 OTBR named[476]: GeoIP City (IPv6) (type 30) DB not available
Sep 24 10:08:26 OTBR named[476]: GeoIP City (IPv6) (type 31) DB not available
Sep 24 10:08:26 OTBR named[476]: GeoIP Region (type 3) DB not available
Sep 24 10:08:26 OTBR named[476]: GeoIP Region (type 7) DB not available
Sep 24 10:08:26 OTBR named[476]: GeoIP ISP (type 4) DB not available
Sep 24 10:08:26 OTBR named[476]: GeoIP Org (type 5) DB not available
Sep 24 10:08:26 OTBR named[476]: GeoIP AS (type 9) DB not available
Sep 24 10:08:26 OTBR named[476]: GeoIP Domain (type 11) DB not available
Sep 24 10:08:26 OTBR named[476]: GeoIP NetSpeed (type 10) DB not available
Sep 24 10:08:26 OTBR named[476]: using default UDP/IPv4 port range: [32768, 60999]
Sep 24 10:08:26 OTBR named[476]: using default UDP/IPv6 port range: [32768, 60999]
Sep 24 10:08:26 OTBR named[476]: listening on IPv6 interface wlan0, fe80::ba27:ebff:fe28:ef7b%3#53
Sep 24 10:08:26 OTBR named[476]: could not listen on UDP socket: address not available
Sep 24 10:08:26 OTBR named[476]: creating IPv6 interface wlan0 failed; interface ignored
Sep 24 10:08:26 OTBR named[476]: sizing zone task pool based on 5 zones
Sep 24 10:08:26 OTBR named[476]: dns64 reverse zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.b.9.f.f.4.6.0.0.ip6.arpa.
Sep 24 10:08:26 OTBR named[476]: using built-in root key for view _default
Sep 24 10:08:26 OTBR named[476]: configuring command channel from '/etc/bind/rndc.key'
Sep 24 10:08:26 OTBR named[476]: configuring command channel from '/etc/bind/rndc.key'
Sep 24 10:08:26 OTBR named[476]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.b.9.f.f.4.6.0.0.ip6.arpa/IN: (master) remo
ved
Sep 24 10:08:26 OTBR named[476]: additionally listening on IPv6 interface wlan0, fe80::ba27:ebff:fe28:ef7b%3#53
Sep 24 10:08:26 OTBR named[476]: could not listen on UDP socket: address not available
Sep 24 10:08:26 OTBR named[476]: creating IPv6 interface wlan0 failed; interface ignored
Sep 24 10:08:26 OTBR named[476]: reloading configuration succeeded
Sep 24 10:08:26 OTBR named[476]: any newly configured zones are now loaded
Sep 24 10:08:26 OTBR systemd[1]: Reloading OpenBSD Secure Shell server.
Sep 24 10:08:26 OTBR sshd[497]: Received SIGHUP; restarting.
Sep 24 10:08:26 OTBR systemd[1]: Reloaded OpenBSD Secure Shell server.
Sep 24 10:08:26 OTBR dhcpv6-helper[1546]: Enable accepting Router Advertisements on the interface: 'wlan0'
Sep 24 10:08:26 OTBR nm-dispatcher[1396]: net.ipv6.conf.wlan0.accept_ra = 2
Sep 24 10:08:26 OTBR dhcpv6-helper[1548]: Starting 'dhcpcd' on the interface: 'wlan0'
Sep 24 10:08:26 OTBR sshd[497]: Server listening on 0.0.0.0 port 22.
Sep 24 10:08:26 OTBR sshd[497]: Server listening on :: port 22.
Sep 24 10:08:26 OTBR dhcpcd[1549]: forked to background, child pid 1550
Sep 24 10:08:26 OTBR dhcpcd[1550]: DUID 00:01:00:01:26:32:09:39:b8:27:eb:b1:ff:fb
Sep 24 10:08:26 OTBR dhcpcd[1550]: wlan0: IAID 00:00:00:04
Sep 24 10:08:26 OTBR dhcpcd[1550]: wlan0: IAID 00:00:00:05
Sep 24 10:08:26 OTBR dhcpcd[1550]: wlan0: IAID 00:00:00:06
Sep 24 10:08:26 OTBR dhcpcd[1550]: wlan0: soliciting an IPv6 router
Sep 24 10:08:27 OTBR dhcpcd[1550]: wlan0: soliciting a DHCPv6 lease
Sep 24 10:08:27 OTBR named[476]: listening on IPv6 interface wlan0, fe80::ba27:ebff:fe28:ef7b%3#53
Sep 24 10:08:27 OTBR dhcpcd[1550]: wpan0: activating for delegation
Sep 24 10:08:27 OTBR avahi-daemon[394]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::
ba27:ebff:fe28:ef7b.
Sep 24 10:08:27 OTBR avahi-daemon[394]: New relevant interface wlan0.IPv6 for mDNS.
Sep 24 10:08:27 OTBR avahi-daemon[394]: Registering new address record for fe80::ba27:ebff:fe28:ef7b on wlan0.*.
Sep 24 10:08:27 OTBR dhcpcd[1550]: wpan0: carrier acquired
Sep 24 10:08:27 OTBR dhcpcd[1550]: wpan0: IAID 00:00:00:0a
Sep 24 10:08:27 OTBR dhcpcd[1550]: wlan0: Router Advertisement from fe80::928d:78ff:fe76:2700
Sep 24 10:08:27 OTBR NetworkManager[385]: <info>  [1663994307.9869] policy: set 'NetweeN' (wlan0) as default for
 IPv6 routing and DNS
Sep 24 10:08:35 OTBR kernel: Voltage normalised (0x00000000)
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  *********************************************************************
******
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  * MQTT-SN Gateway
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  * Part of Project Paho in Eclipse
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  * (http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt-sn.embedded-c.
git/)
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  *
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  * Author : Tomoaki YAMAGUCHI
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  * Version: 1.5.1
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  *********************************************************************
******
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100712.501 PahoGateway-01 has been started.
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  ConfigFile: /etc/paho-mqtt-sn-gateway.conf
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  SensorN/W:   Gateway Port: 47193 Broadcast Address: ff33:40:fdde:ad00
:beef:0:0:1 Interface: wpan0 Hops: 5
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  Broker:     103.238.13.202 : 1883, 8883
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  Max number of Clients: 10000
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  RootCApath: (null)
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  RootCAfile: (null)
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  CertKey:    (null)
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]:  PrivateKey: (null)
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100720.422   SEARCHGW          <---  Client                  
            03 01 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100720.422   GWINFO            --->  Clients                 
            03 02 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100726.245   SEARCHGW          <---  Client                  
            03 01 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100726.245   GWINFO            --->  Clients                 
            03 02 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100731.284   SEARCHGW          <---  Client                  
            03 01 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100731.284   GWINFO            --->  Clients                 
            03 02 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100735.680   SEARCHGW          <---  Client                  
            03 01 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100735.680   GWINFO            --->  Clients                 
            03 02 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100740.901   SEARCHGW          <---  Client                  
            03 01 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100740.902   GWINFO            --->  Clients                 
            03 02 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100807.641   SEARCHGW          <---  Client                  
            03 01 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100807.641   GWINFO            --->  Clients                 
            03 02 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100818.458   SEARCHGW          <---  Client                  
            03 01 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100818.459   GWINFO            --->  Clients                 
            03 02 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100822.312   SEARCHGW          <---  Client                  
            03 01 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100822.313   GWINFO            --->  Clients                 
            03 02 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100827.876   SEARCHGW          <---  Client                  
            03 01 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100827.876   GWINFO            --->  Clients                 
            03 02 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100832.133   SEARCHGW          <---  Client                  
            03 01 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100832.133   GWINFO            --->  Clients                 
            03 02 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100837.475   SEARCHGW          <---  Client                  
            03 01 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100837.476   GWINFO            --->  Clients                 
            03 02 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100842.714   SEARCHGW          <---  Client                  
            03 01 01
Sep 24 10:08:47 OTBR MQTT-SNGateway[557]: 20220924 100842.714   GWINFO            --->  Clients                 
            03 02 01
[   88.710498] Under-voltage detected! (0x00050005)
Sep 24 10:08:49 OTBR kernel: Under-voltage detected! (0x00050005)
Sep 24 10:08:54 OTBR kernel: Voltage normalised (0x00000000)
Sep 24 10:09:01 OTBR CRON[1565]: pam_unix(cron:session): session opened for user pi by (uid=0)
Sep 24 10:09:01 OTBR CRON[1564]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 24 10:09:01 OTBR CRON[1572]: (root) CMD (/home/pi/Autorun/reboot_wpan0sh >> /home/pi/rtxt.txt)
Sep 24 10:09:01 OTBR CRON[1573]: (pi) CMD (/home/pi/Autorun/reboot_wpan0.sh )
Sep 24 10:09:01 OTBR CRON[1564]: (CRON) info (No MTA installed, discarding output)
Sep 24 10:09:01 OTBR CRON[1564]: pam_unix(cron:session): session closed for user root
Sep 24 10:09:01 OTBR CRON[1565]: (CRON) info (No MTA installed, discarding output)
Sep 24 10:09:01 OTBR CRON[1565]: pam_unix(cron:session): session closed for user pi

How to solve this issue ?

RE: Nordic Border Router suddenly stopped working

Sigurd Hellesvik — Fri, 23 Sep 2022 11:03:37 GMT

Hi,

See the arch wiki on DHCP Client Identifier.

Try to statically set iaid in /etc/dhcpcd.conf

Regards,
Sigurd Hellesvik

RE: Nordic Border Router suddenly stopped working

Brian (Geek) — Thu, 22 Sep 2022 12:30:10 GMT

Hello suddenly the same issue has arrived again.

OTBR dhcpcd[1099]: wpan0: IAID conflicts with one assigned to wlan0

I have stopped and started the dhcpd service in RPI still it gives the same issue.

How to resolve ?

RE: Nordic Border Router suddenly stopped working

Brian (Geek) — Mon, 17 Jan 2022 10:16:10 GMT

[quote userid="106736" url="~/f/nordic-q-a/83619/nordic-border-router-suddenly-stopped-working/347936#347936"]To test if this will happen every time dhcpcd is run, or if it opnly happens if unluckt, try to run "dhcpcd" from your Raspberry Pi command line and check the error logs after. Do this several times.[/quote]

okay thanks i will let you know after checking.

RE: Nordic Border Router suddenly stopped working

Sigurd Hellesvik — Mon, 17 Jan 2022 08:30:59 GMT

The error message in your image is tagged "dhcpcd[1945]", so my guess is that this is a dhcpcd error.

I suspect that the Raspberry Pi runs dhcpcd regularly. And by chance, it tried to give the same address to wlan0 and wpan0 when it crashed.

To test if this will happen every time dhcpcd is run, or if it opnly happens if unluckt, try to run "dhcpcd" from your Raspberry Pi command line and check the error logs after. Do this several times.

Regards,
Sigurd Hellesvik

RE: Nordic Border Router suddenly stopped working

Brian (Geek) — Mon, 17 Jan 2022 03:26:36 GMT

Okay is that a dhcpcd error ?

As i have less knowledge of networking , i would like to know will restarting dhcpd service solve that ?

RE: Nordic Border Router suddenly stopped working

Sigurd Hellesvik — Thu, 13 Jan 2022 13:46:38 GMT

Hi Brian

Thank you for reporting this. I suspect it is a bug, and will inform our developers.

As a workaround, I suggest that you make the Border Router rerun dhcpcd after you detect the error.

Regards,
Sigurd Hellesvik