nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8 - thread cli example not able to ping 64:ff9b::0808:0808

[Achim Kraus]

Environment:

DSL-Router, IPv4 only, DHCPv6 disabled

Raspberry PI 3B, RaspPi_OT_Border_Router_Demo_v4.1.0-1.alpha.img, the raspberry is connected via wire with the dsl-router.

2x nrf52840, version 1.0.0

- one with nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8/examples/thread/ncp/ftd/uart/hex/nrf52840_xxaa_pca10056.hex (connected to the raspberry)

- one with nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8/examples/thread/cli/ftd/uart/hex/nrf52840_xxaa_pca10056.hex (connected to serial terminal)

--------------------------------------------------------

From the raspberries cli it's possible to ping 8.8.8.8 or 64:ff9b::0808:0808 (so NAT64 works).

The cli node is setup as documented with:

> panid 0xabcd
Done
> ifconfig up
Done
> thread start
Done
> state
child
Done
> state
child
Done
> ipaddr
fdde:ad00:beef:0:0:ff:fe00:b002
fdde:ad00:beef:0:a906:88a7:7dba:29ac
fe80:0:0:0:38aa:9654:1234:320c
Done

From the cli node, it's possible to ping the raspberry

> ping fdde:ad00:beef:0:1b19:99dd:817:405d
> 16 bytes from fdde:ad00:beef:0:1b19:99dd:817:405d: icmp_seq=2 hlim=64 time=37ms

(tcpdump on raspberry).

06:06:49.153481 IP6 fdde:ad00:beef:0:a906:88a7:7dba:29ac > fdde:ad00:beef:0:1b19:99dd:817:405d: ICMP6, echo request, seq 2, length 16
06:06:49.153613 IP6 fdde:ad00:beef:0:1b19:99dd:817:405d > fdde:ad00:beef:0:a906:88a7:7dba:29ac: ICMP6, echo reply, seq 2, length 16

But  ping 64:ff9b::0808:0808 from the cli node doesn't work.

> ping 64:ff9b::0808:0808
> ping 64:ff9b::0808:0808

(tcpdump on raspberry shows no traffic).

--------------------------------------------------------

Question:

What is required to make the cli node routing/sending the "ping 64:ff9b::0808:0808"?

[Jørgen Holmefjord]

Hi,

It looks like you are missing the IPv6 address from the Wpantund interface (Default: on-mesh prefix "fd11:22::/64"):

> ipaddr
fd11:22:0:0:4567:cc67:5831:d8a3
fdde:ad00:beef:0:0:ff:fe00:8000
fdde:ad00:beef:0:c785:680f:db44:e436
fe80:0:0:0:9895:490:5998:65a7
Done
> ping 64:ff9b::0808:0808
Done
> 16 bytes from 64:ff9b:0:0:0:0:808:808: icmp_seq=1 hlim=110 time=110ms

Without the fd11:22::/64 address, you will not be able to reach internet through the Border Router. You can try power cycling the NCP, and then run "sudo wpantund" to bring up the NCP again:

pi@raspberrypi:~ $ sudo wpantund &
[1] 3041
pi@raspberrypi:~ $ wpantund[3045]: Starting wpantund 0.08.00d (Dec 13 2019 21:37:34) . . .
wpantund[3045]: Configuration file "/etc/wpantund.conf" read.
wpantund[3045]: Ready. Using DBUS bus ":1.380"
wpantund[3045]: Running as root without dropping privileges!
wpantund[3045]: State change: "uninitialized" -> "offline"
wpantund[3045]: NCP is running "OPENTHREAD/20191113-00534-gc6a258e3; NRF52840; Apr  5 2020 21:51:18"
wpantund[3045]: Driver is running "0.08.00d (; Dec 13 2019 21:37:34)"
wpantund[3045]: Network is not joinable
wpantund[3045]: State change: "offline" -> "offline:commissioned"
wpantund[3045]: [-NCP-]: SLAAC enabled
wpantund[3045]: Finished initializing NCP
wpantund[3045]: AutoResume is enabled. Trying to resume.
wpantund[3045]: NCP is commissioned. Resuming...
wpantund[3045]: State change: "offline:commissioned" -> "associating"
wpantund[3045]: State change: "associating" -> "associated"
wpantund[3045]: Node type change: "unknown" -> "leader"
wpantund[3045]: Adding on-mesh prefix "fd11:22::/64" to NCP

Best regards,
Jørgen

[Achim Kraus]

Thanks a lot!

Seems, that this fd11:22 only shows up randomly. If it's there, it works, as you wrote.

Are there know startup issues? Maybe "power supply"?