This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

How to test Thread while using Ubuntu docker as OTBR

Hi ,

I had done the user guide on https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.6.1/nrf/ug_matter_configuring.html#ug-matter-configuring , could you please tell how to test next step,Thanks!

I use 52840dongle + Ubuntu docker as OTBR,and program one  /ncs/nrf/samples/matter/light_bulb on 52840DK . The 52840DK hulb node works when press button2 led2 will toggle.

On the OTBR side ,after typing 

sudo docker run -it --rm --privileged --name otbr --network otbr -p 8080:80 \
--sysctl "net.ipv6.conf.all.disable_ipv6=0 net.ipv4.conf.all.forwarding=1 net.ipv6.conf.all.forwarding=1" \
--volume /dev/ttyACM0:/dev/radio openthread/otbr --radio-url spinel+hdlc+uart:///dev/radio

It will show lots of logs:

simon@ubuntu:~$ sudo docker run -it --rm --privileged --name otbr --network otbr -p 8080:80 \
> --sysctl "net.ipv6.conf.all.disable_ipv6=0 net.ipv4.conf.all.forwarding=1 net.ipv6.conf.all.forwarding=1" \
> --volume /dev/ttyACM0:/dev/radio openthread/otbr --radio-url spinel+hdlc+uart:///dev/radio
[sudo] simon 的密码: 
RADIO_URL: spinel+hdlc+uart:///dev/radio
TUN_INTERFACE_NAME: wpan0
BACKBONE_INTERFACE: eth0
NAT64_PREFIX: 64:ff9b::/96
AUTO_PREFIX_ROUTE: true
AUTO_PREFIX_SLAAC: true
+++ dirname /app/script/server
++ cd /app/script/..
++ [[ ! -n x ]]
++ echo 'Current platform is ubuntu'
Current platform is ubuntu
++ with BORDER_ROUTING
++ local value
+++ printenv BORDER_ROUTING
++ value=1
++ [[ -z 1 ]]
++ [[ 1 == 1 ]]
++ with DHCPV6_PD
++ local value
+++ printenv DHCPV6_PD
++ value=
++ [[ -z '' ]]
++ [[ -f examples/platforms/ubuntu/default ]]
++ [[ '' == 1 ]]
++ with BORDER_ROUTING
++ local value
+++ printenv BORDER_ROUTING
++ value=1
++ [[ -z 1 ]]
++ [[ 1 == 1 ]]
++ with NETWORK_MANAGER
++ local value
+++ printenv NETWORK_MANAGER
++ value=
++ [[ -z '' ]]
++ [[ -f examples/platforms/ubuntu/default ]]
++ [[ '' == 1 ]]
++ STAGE_DIR=/app/stage
++ BUILD_DIR=/app/build
++ [[ -d /app/stage ]]
++ mkdir -v -p /app/stage
mkdir: created directory '/app/stage'
++ [[ -d /app/build ]]
++ mkdir -v -p /app/build
mkdir: created directory '/app/build'
++ export PATH=/app/stage/usr/bin:/app/stage/usr/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
++ PATH=/app/stage/usr/bin:/app/stage/usr/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
+++ basename /app/script/server
++ TASKNAME=server
++ BEFORE_HOOK=examples/platforms/ubuntu/before_server
++ AFTER_HOOK=examples/platforms/ubuntu/after_server
++ [[ ! -f examples/platforms/ubuntu/before_server ]]
++ BEFORE_HOOK=/dev/null
++ [[ ! -f examples/platforms/ubuntu/after_server ]]
++ AFTER_HOOK=/dev/null
+ . script/_nat64
++ TAYGA_DEFAULT=/etc/default/tayga
++ TAYGA_CONF=/etc/tayga.conf
++ TAYGA_IPV4_ADDR=192.168.255.1
++ TAYGA_IPV6_ADDR=fdaa:bb:1::1
++ TAYGA_TUN_V6_ADDR=fdaa:bb:1::2
++ NAT44_SERVICE=/etc/init.d/otbr-nat44
++ WLAN_IFNAMES=eth0
+ . script/_dns64
++ BIND_CONF_OPTIONS=/etc/bind/named.conf.options
++ NAT64_PREFIX=64:ff9b::/96
++ DNS64_NAMESERVER_ADDR=127.0.0.1
+++ echo 64:ff9b::/96
+++ tr '"/"' '"/"'
++ DNS64_CONF='dns64 64:ff9b::/96 { clients { thread; }; recursive-only yes; };'
++ without NAT64
++ with NAT64
++ local value
+++ printenv NAT64
++ value=1
++ [[ -z 1 ]]
++ [[ 1 == 1 ]]
++ test ubuntu = ubuntu
++ '[' ubuntu = raspbian ']'
++ '[' ubuntu = beagleboneblack ']'
++ '[' ubuntu = ubuntu ']'
++ RESOLV_CONF_HEAD=/etc/resolvconf/resolv.conf.d/head
+ main
+ . /dev/null
+ sudo sysctl --system
* Applying /etc/sysctl.d/10-console-messages.conf ...
kernel.printk = 4 4 1 7
* Applying /etc/sysctl.d/10-ipv6-privacy.conf ...
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2
* Applying /etc/sysctl.d/10-kernel-hardening.conf ...
kernel.kptr_restrict = 1
* Applying /etc/sysctl.d/10-link-restrictions.conf ...
fs.protected_hardlinks = 1
fs.protected_symlinks = 1
* Applying /etc/sysctl.d/10-magic-sysrq.conf ...
kernel.sysrq = 176
* Applying /etc/sysctl.d/10-network-security.conf ...
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
net.ipv4.tcp_syncookies = 1
* Applying /etc/sysctl.d/10-ptrace.conf ...
kernel.yama.ptrace_scope = 1
* Applying /etc/sysctl.d/10-zeropage.conf ...
vm.mmap_min_addr = 65536
* Applying /etc/sysctl.d/60-otbr-accept-ra.conf ...
net.ipv6.conf.eth0.accept_ra = 2
net.ipv6.conf.eth0.accept_ra_rt_info_max_plen = 64
* Applying /etc/sysctl.d/60-otbr-ip-forward.conf ...
net.ipv6.conf.all.forwarding = 1
net.ipv4.ip_forward = 1
* Applying /etc/sysctl.conf ...
+ nat64_start
+ with NAT64
+ local value
++ printenv NAT64
+ value=1
+ [[ -z 1 ]]
+ [[ 1 == 1 ]]
+ with DOCKER
+ local value
++ printenv DOCKER
+ value=1
+ [[ -z 1 ]]
+ [[ 1 == 1 ]]
+ service tayga start
 * Starting userspace NAT64 tayga                                                                                                                                                                    [ OK ] 
+ dns64_start
+ with NAT64
+ local value
++ printenv NAT64
+ value=1
+ [[ -z 1 ]]
+ [[ 1 == 1 ]]
+ with DNS64
+ local value
++ printenv DNS64
+ value=1
+ [[ -z 1 ]]
+ [[ 1 == 1 ]]
++ _detect_service_name
++ dpkg -L bind9
++ grep /etc/init.d/
++ cut -d/ -f4
+ service_name=bind9
+ have systemctl
+ command -v systemctl
+ command -v service
/usr/sbin/service
+ sudo service bind9 start
 * Starting domain name service... bind9                                                                                                                                                             [ OK ] 
+ have systemctl
+ command -v systemctl
+ have service
+ command -v service
+ sudo service rsyslog status
 * rsyslogd is not running
+ sudo service rsyslog start
 * Starting enhanced syslogd rsyslogd                                                                                                                                                                [ OK ] 
+ sudo service dbus status
 * dbus is not running
+ sudo service dbus start
 * Starting system message bus dbus                                                                                                                                                                  [ OK ] 
+ sudo service mdns status
Usage: /etc/init.d/mDNS {start|stop|reload|restart}
+ sudo service mdns start
Starting Apple Darwin Multicast DNS / DNS Service Discovery daemon: mdnsd.
+ sudo service avahi-daemon status
Avahi mDNS/DNS-SD Daemon is not running
+ sudo service avahi-daemon start
 * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon                                                                                                                                                    [ OK ] 
+ sudo service otbr-agent status
 * otbr-agent is not running
+ sudo service otbr-agent start
 * Starting thread border agent otbr-agent                                                                                                                                                           [ OK ] 
+ without WEB_GUI
+ with WEB_GUI
+ local value
++ printenv WEB_GUI
+ value=1
+ [[ -z 1 ]]
+ [[ 1 == 1 ]]
+ sudo service otbr-web status
 * otbr-web is not running
+ sudo service otbr-web start
 * Starting thread web interface otbr-web                                                                                                                                                            [ OK ] 
+ . /dev/null
Sep 17 09:44:41 56b1fd377ebd avahi-daemon[187]: New relevant interface eth0.IPv4 for mDNS.
Sep 17 09:44:41 56b1fd377ebd avahi-daemon[187]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
Sep 17 09:44:41 56b1fd377ebd avahi-daemon[187]: New relevant interface lo.IPv6 for mDNS.
Sep 17 09:44:41 56b1fd377ebd avahi-daemon[187]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Sep 17 09:44:41 56b1fd377ebd avahi-daemon[187]: New relevant interface lo.IPv4 for mDNS.
Sep 17 09:44:41 56b1fd377ebd avahi-daemon[187]: Network interface enumeration completed.
Sep 17 09:44:41 56b1fd377ebd avahi-daemon[187]: Registering new address record for fd11:db8:1::2 on eth0.*.
Sep 17 09:44:41 56b1fd377ebd avahi-daemon[187]: Registering new address record for 172.18.0.2 on eth0.IPv4.
Sep 17 09:44:41 56b1fd377ebd avahi-daemon[187]: Registering new address record for ::1 on lo.*.
Sep 17 09:44:41 56b1fd377ebd avahi-daemon[187]: Registering new address record for 127.0.0.1 on lo.IPv4.
Sep 17 09:44:41 56b1fd377ebd otbr-agent[215]: [INFO]-UTILS---: Running 0.3.0-9c5aa1c
Sep 17 09:44:41 56b1fd377ebd otbr-agent[215]: [INFO]-UTILS---: Thread version: 1.2.0
Sep 17 09:44:41 56b1fd377ebd otbr-agent[215]: [INFO]-UTILS---: Thread interface: wpan0
Sep 17 09:44:41 56b1fd377ebd otbr-agent[215]: [INFO]-UTILS---: Backbone interface: eth0
Sep 17 09:44:41 56b1fd377ebd otbr-agent[215]: [INFO]-UTILS---: Radio URL: spinel+hdlc+uart:///dev/radio
Sep 17 09:44:41 56b1fd377ebd otbr-agent[215]: [INFO]-PLAT----: RCP reset: RESET_POWER_ON
Sep 17 09:44:42 56b1fd377ebd otbr-agent[215]: [NOTE]-PLAT----: RCP API Version: 4
Sep 17 09:44:42 56b1fd377ebd otbr-agent[215]: [INFO]-PLAT----: Backbone interface is configured to eth0 (7)
Sep 17 09:44:42 56b1fd377ebd otbr-agent[215]: [INFO]-AGENT---: Set state callback: OK
Sep 17 09:44:42 56b1fd377ebd otbr-agent[215]: [INFO]-AGENT---: Stop Thread Border Agent
Sep 17 09:44:42 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Stopped
Sep 17 09:44:42 56b1fd377ebd otbr-agent[215]: [INFO]-DPROXY--: stopped
Sep 17 09:44:42 56b1fd377ebd otbr-agent[215]: [INFO]-AGENT---: Initialize OpenThread Border Router Agent: OK
Sep 17 09:44:42 56b1fd377ebd otbr-web[243]: [INFO]-WEB-----: Running 0.3.0-9c5aa1c
Sep 17 09:44:42 56b1fd377ebd otbr-web[243]: [INFO]-WEB-----: Border router web started on wpan0
Sep 17 09:44:42 56b1fd377ebd otbr-agent[215]: [INFO]-UTILS---: Border router agent started.
Sep 17 09:44:42 56b1fd377ebd otbr-agent[215]: [DEBG]-BBA-----: BackboneAgent: HandleBackboneRouterState: state=1, mBackboneRouterState=0
Sep 17 09:44:42 56b1fd377ebd named[87]: managed-keys-zone: Key 20326 for zone . acceptance timer complete: key now trusted
Sep 17 09:44:42 56b1fd377ebd avahi-daemon[187]: Server startup complete. Host name is 56b1fd377ebd.local. Local service cookie is 3056352893.
Sep 17 09:44:42 56b1fd377ebd rsyslogd: rsyslogd's groupid changed to 101
Sep 17 09:44:42 56b1fd377ebd rsyslogd: rsyslogd's userid changed to 101
Sep 17 09:44:42 56b1fd377ebd rsyslogd:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="120" x-info="http://www.rsyslog.com"] start
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [INFO]-UTILS---: Running 0.3.0-9c5aa1c
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [INFO]-UTILS---: Thread version: 1.2.0
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [INFO]-UTILS---: Thread interface: wpan0
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [INFO]-UTILS---: Backbone interface: eth0
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [INFO]-UTILS---: Radio URL: spinel+hdlc+uart:///dev/radio
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [INFO]-PLAT----: RCP reset: RESET_POWER_ON
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [NOTE]-PLAT----: RCP API Version: 4
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [INFO]-PLAT----: Backbone interface is configured to eth0 (7)
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [INFO]-AGENT---: Set state callback: OK
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [INFO]-AGENT---: Stop Thread Border Agent
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Stopped
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [INFO]-DPROXY--: stopped
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [INFO]-AGENT---: Initialize OpenThread Border Router Agent: OK
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [INFO]-UTILS---: Border router agent started.
Sep 17 09:45:50 56b1fd377ebd otbr-agent[215]: [DEBG]-BBA-----: BackboneAgent: HandleBackboneRouterState: state=1, mBackboneRouterState=0
Sep 17 09:45:54 56b1fd377ebd otbr-agent[215]: [INFO]-AGENT---: Thread is down
Sep 17 09:45:54 56b1fd377ebd otbr-agent[215]: [INFO]-AGENT---: Stop Thread Border Agent
Sep 17 09:45:54 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Stopped
Sep 17 09:45:54 56b1fd377ebd otbr-agent[215]: [INFO]-DPROXY--: stopped
Sep 17 09:45:54 56b1fd377ebd otbr-agent[215]: [DEBG]-UTILS---: Signal io.openthread.BorderRouter.DeviceRole
Sep 17 09:45:54 56b1fd377ebd otbr-agent[215]: [DEBG]-DBUS----: { "io.openthread.BorderRouter", [ DeviceRole:{ "detached", }, ], [ ], }
Sep 17 09:45:54 56b1fd377ebd named[87]: listening on IPv6 interface wpan0, fdfd:3a5d:b921:ff9f:9c19:dd09:8ef6:7355#53
Sep 17 09:45:54 56b1fd377ebd named[87]: listening on IPv6 interface wpan0, fe80::106c:ca90:d7d:f68%4#53
Sep 17 09:45:56 56b1fd377ebd named[87]: listening on IPv6 interface wpan0, fdfd:3a5d:b921:ff9f:0:ff:fe00:fc00#53
Sep 17 09:45:56 56b1fd377ebd otbr-agent[215]: [INFO]-AGENT---: Thread is up
Sep 17 09:45:56 56b1fd377ebd otbr-agent[215]: [INFO]-AGENT---: Stop Thread Border Agent
Sep 17 09:45:56 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Stopped
Sep 17 09:45:56 56b1fd377ebd otbr-agent[215]: [INFO]-DPROXY--: stopped
Sep 17 09:45:56 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Started
Sep 17 09:45:56 56b1fd377ebd otbr-agent[215]: [INFO]-AGENT---: Publish meshcop service OpenThread_BorderRouter._meshcop._udp.local.
Sep 17 09:45:56 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Add service: OpenThread_BorderRouter._meshcop._udp (ref: 0x55f1ee050140)
Sep 17 09:45:56 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Publish all hosts and services
Sep 17 09:45:56 56b1fd377ebd otbr-agent[215]: [INFO]-DPROXY--: started
Sep 17 09:45:56 56b1fd377ebd otbr-agent[215]: [INFO]-AGENT---: Start Thread Border Agent: OK
Sep 17 09:45:56 56b1fd377ebd named[87]: listening on IPv6 interface wpan0, fdfd:3a5d:b921:ff9f:0:ff:fe00:3000#53
Sep 17 09:45:56 56b1fd377ebd otbr-agent[215]: [DEBG]-UTILS---: Signal io.openthread.BorderRouter.DeviceRole
Sep 17 09:45:56 56b1fd377ebd otbr-agent[215]: [DEBG]-DBUS----: { "io.openthread.BorderRouter", [ DeviceRole:{ "leader", }, ], [ ], }
Sep 17 09:45:56 56b1fd377ebd named[87]: listening on IPv6 interface wpan0, fd11:22::9aaf:d3f5:22a5:926b#53
Sep 17 09:45:57 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Received reply for service OpenThread_BorderRouter._meshcop._udp.
Sep 17 09:45:57 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Successfully registered service OpenThread_BorderRouter._meshcop._udp.
Sep 17 09:45:57 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Handle publish service 'OpenThread_BorderRouter._meshcop._udp.' result: 0
Sep 17 09:45:57 56b1fd377ebd otbr-agent[215]: [INFO]-AGENT---: Publish meshcop service OpenThread_BorderRouter._meshcop._udp.local.
Sep 17 09:45:57 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Update service OpenThread_BorderRouter._meshcop._udp
Sep 17 09:45:57 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Handle publish service 'OpenThread_BorderRouter._meshcop._udp' result: 0
Sep 17 09:45:57 56b1fd377ebd otbr-agent[215]: [DEBG]-BBA-----: BackboneAgent: HandleBackboneRouterState: state=2, mBackboneRouterState=1
Sep 17 09:45:57 56b1fd377ebd otbr-agent[215]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
Sep 17 09:45:57 56b1fd377ebd named[87]: listening on IPv6 interface wpan0, fdfd:3a5d:b921:ff9f:0:ff:fe00:fc10#53
Sep 17 09:45:57 56b1fd377ebd named[87]: listening on IPv6 interface wpan0, fdfd:3a5d:b921:ff9f:0:ff:fe00:fc38#53
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Withdrawing address record for fd11:db8:1::2 on eth0.
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Withdrawing address record for 172.18.0.2 on eth0.
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Withdrawing address record for 127.0.0.1 on lo.
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Host name conflict, retrying with 56b1fd377ebd-2
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Registering new address record for fd11:db8:1::2 on eth0.*.
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Registering new address record for 172.18.0.2 on eth0.IPv4.
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Registering new address record for ::1 on lo.*.
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Registering new address record for 127.0.0.1 on lo.IPv4.
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Withdrawing address record for fd11:db8:1::2 on eth0.
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Withdrawing address record for ::1 on lo.
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Withdrawing address record for 127.0.0.1 on lo.
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Host name conflict, retrying with 56b1fd377ebd-3
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Registering new address record for fd11:db8:1::2 on eth0.*.
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Registering new address record for 172.18.0.2 on eth0.IPv4.
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Registering new address record for ::1 on lo.*.
Sep 17 09:45:57 56b1fd377ebd avahi-daemon[187]: Registering new address record for 127.0.0.1 on lo.IPv4.
Sep 17 09:45:58 56b1fd377ebd avahi-daemon[187]: Withdrawing address record for fd11:db8:1::2 on eth0.
Sep 17 09:45:58 56b1fd377ebd avahi-daemon[187]: Withdrawing address record for ::1 on lo.
Sep 17 09:45:58 56b1fd377ebd avahi-daemon[187]: Withdrawing address record for 127.0.0.1 on lo.
Sep 17 09:45:58 56b1fd377ebd avahi-daemon[187]: Host name conflict, retrying with 56b1fd377ebd-4
Sep 17 09:45:58 56b1fd377ebd avahi-daemon[187]: Registering new address record for fd11:db8:1::2 on eth0.*.
Sep 17 09:45:58 56b1fd377ebd avahi-daemon[187]: Registering new address record for 172.18.0.2 on eth0.IPv4.
Sep 17 09:45:58 56b1fd377ebd avahi-daemon[187]: Registering new address record for ::1 on lo.*.
Sep 17 09:45:58 56b1fd377ebd avahi-daemon[187]: Registering new address record for 127.0.0.1 on lo.IPv4.
Sep 17 09:45:58 56b1fd377ebd named[87]: listening on IPv6 interface wpan0, fdfd:3a5d:b921:ff9f:0:ff:fe00:fc11#53
Sep 17 09:46:00 56b1fd377ebd avahi-daemon[187]: Withdrawing address record for 172.18.0.2 on eth0.
Sep 17 09:46:00 56b1fd377ebd avahi-daemon[187]: Withdrawing address record for ::1 on lo.
Sep 17 09:46:00 56b1fd377ebd avahi-daemon[187]: Withdrawing address record for 127.0.0.1 on lo.
Sep 17 09:46:00 56b1fd377ebd avahi-daemon[187]: Host name conflict, retrying with 56b1fd377ebd-5
Sep 17 09:46:00 56b1fd377ebd avahi-daemon[187]: Registering new address record for fd11:db8:1::2 on eth0.*.
Sep 17 09:46:00 56b1fd377ebd avahi-daemon[187]: Registering new address record for 172.18.0.2 on eth0.IPv4.
Sep 17 09:46:00 56b1fd377ebd avahi-daemon[187]: Registering new address record for ::1 on lo.*.
Sep 17 09:46:00 56b1fd377ebd avahi-daemon[187]: Registering new address record for 127.0.0.1 on lo.IPv4.
Sep 17 09:46:01 56b1fd377ebd avahi-daemon[187]: Server startup complete. Host name is 56b1fd377ebd-5.local. Local service cookie is 3056352893.
Sep 17 09:46:01 56b1fd377ebd mDNSResponder: mDNSCoreReceiveResponse: Received from 172.18.0.2:5353   22 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.8.b.d.0.1.1.d.f.ip6.arpa. PTR 56b1fd377ebd-5.local.
Sep 17 09:46:01 56b1fd377ebd mDNSResponder: mDNSCoreReceiveResponse: Unexpected conflict discarding   20 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.8.B.D.0.1.1.D.F.ip6.arpa. PTR 56b1fd377ebd.local.
Sep 17 09:46:01 56b1fd377ebd mDNSResponder: mDNSCoreReceiveResponse: Received from 172.18.0.2:5353   22 2.0.18.172.in-addr.arpa. PTR 56b1fd377ebd-5.local.
Sep 17 09:46:01 56b1fd377ebd mDNSResponder: mDNSCoreReceiveResponse: Unexpected conflict discarding   20 2.0.18.172.in-addr.arpa. PTR 56b1fd377ebd.local.
Sep 17 09:46:08 56b1fd377ebd avahi-daemon[187]: Registering new address record for fd7c:1caf:6935:0:42:acff:fe12:2 on eth0.*.
Sep 17 09:46:08 56b1fd377ebd named[87]: listening on IPv6 interface eth0, fd7c:1caf:6935:0:42:acff:fe12:2#53
Sep 17 09:46:49 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Advertise SRP service updates: host=126F81E0F11D3A2F.default.service.arpa.
Sep 17 09:46:49 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Publish SRP host: 126F81E0F11D3A2F.default.service.arpa.
Sep 17 09:46:49 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Publish new host 126F81E0F11D3A2F
Sep 17 09:46:49 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Add new host 126F81E0F11D3A2F
Sep 17 09:46:49 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Publish SRP service: 000000014A77CBB3-0000000000BC5C01._chip._tcp.default.service.arpa.
Sep 17 09:46:49 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Add service: 000000014A77CBB3-0000000000BC5C01._chip._tcp (ref: 0x55f1ee052d40)
Sep 17 09:46:50 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Received reply for service 000000014A77CBB3-0000000000BC5C01._chip._tcp.
Sep 17 09:46:50 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Successfully registered service 000000014A77CBB3-0000000000BC5C01._chip._tcp.
Sep 17 09:46:50 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Handle publish service '000000014A77CBB3-0000000000BC5C01._chip._tcp.' result: 0
Sep 17 09:46:50 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Received reply for host 126F81E0F11D3A2F
Sep 17 09:46:50 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Successfully registered host 126F81E0F11D3A2F
Sep 17 09:46:50 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Handle publish host '126F81E0F11D3A2F' result: 0
Sep 17 09:46:51 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Advertise SRP service updates: host=126F81E0F11D3A2F.default.service.arpa.
Sep 17 09:46:51 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Publish SRP host: 126F81E0F11D3A2F.default.service.arpa.
Sep 17 09:46:51 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Update existing host 126F81E0F11D3A2F
Sep 17 09:46:51 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Update existing host 126F81E0F11D3A2F
Sep 17 09:46:51 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Handle publish host '126F81E0F11D3A2F' result: 0
Sep 17 09:46:51 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Publish SRP service: 000000014A77CBB3-0000000000BC5C01._chip._tcp.default.service.arpa.
Sep 17 09:46:51 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Update service 000000014A77CBB3-0000000000BC5C01._chip._tcp
Sep 17 09:46:51 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Handle publish service '000000014A77CBB3-0000000000BC5C01._chip._tcp' result: 0
Sep 17 09:46:54 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Advertise SRP service updates: host=126F81E0F11D3A2F.default.service.arpa.
Sep 17 09:46:54 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Publish SRP host: 126F81E0F11D3A2F.default.service.arpa.
Sep 17 09:46:54 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Update existing host 126F81E0F11D3A2F
Sep 17 09:46:54 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Update existing host 126F81E0F11D3A2F
Sep 17 09:46:54 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Handle publish host '126F81E0F11D3A2F' result: 0
Sep 17 09:46:54 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Publish SRP service: 000000014A77CBB3-0000000000BC5C01._chip._tcp.default.service.arpa.
Sep 17 09:46:54 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Update service 000000014A77CBB3-0000000000BC5C01._chip._tcp
Sep 17 09:46:54 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Handle publish service '000000014A77CBB3-0000000000BC5C01._chip._tcp' result: 0
Sep 17 09:47:00 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Advertise SRP service updates: host=126F81E0F11D3A2F.default.service.arpa.
Sep 17 09:47:00 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Publish SRP host: 126F81E0F11D3A2F.default.service.arpa.
Sep 17 09:47:00 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Update existing host 126F81E0F11D3A2F
Sep 17 09:47:00 56b1fd377ebd otbr-agent[215]: [INFO]-MDNS----: Update existing host 126F81E0F11D3A2F
Sep 17 09:47:00 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Handle publish host '126F81E0F11D3A2F' result: 0
Sep 17 09:47:00 56b1fd377ebd otbr-agent[215]: [INFO]-ADPROXY-: Publish SRP service: 000000014A77CBB3-0000000000BC5C01._chip._tcp.default.service.arpa.

so it means works? And http://localhost:8080/ also can show the OTBR website content , and Form Thread Networks also success.

Check state:

simon@ubuntu:~/Nordic/ncs/ncs/nrf/samples/matter/light_bulb$ sudo docker exec -it otbr sh -c "sudo service otbr-agent status"
 * otbr-agent is running
simon@ubuntu:~/Nordic/ncs/ncs/nrf/samples/matter/light_bulb$ sudo docker exec -it otbr sh -c "sudo ot-ctl state"
leader
Done

  • Hi OPQ

    To check that the thread network connects as it should, the nRF Thread topology monitor is useful. This can be run on an external computer (Not the OTBR), and connect to the Thread network as a new node.

    The 52840DK hulb node works when press button2 led2 will toggle.

    This will happen as long as the nRF52840DK is programmed properly, and does not require the DK to be connected to a Matter network.

    To find if you can toggle the led from another device, you could follow the next step of the tutorial:

    "Testing with the Python Matter Controller - see Working with Python Controller in the Matter documentation"

    You should be able to control the LED on the nRF52840DK Matter light bulb from the Python Controller.

    If you want your thread network to be connected to the internet, you can check if it can ping Google. This will try to ping the ipv6-equivalent of 8.8.8.8:

    sudo ot-ctl ping 64:ff9b::0808:0808

    If you have other questions, let me know,

    Regards,
    Sigurd Hellesvik

Related