Devices cannot ping internet - fresh otbr build for eth0 interface

mjkuwp94

unread,

Apr 7, 2021, 10:15:04 AM4/7/21

to openthread-users

Hello,

as the subject says I have built a new thread network with a Raspberry Pi 3B+ with the latest OS and a Nordic pca10059 dongle as the RCP. I also have two FTD Nordic Dongles and succesfully(it appears) made a network of 3 devices as shown on the topology page of the gui.

I did the commissioning with the command line in the border router because I could not get the ThreadGroup Android app to work (sometimes it has worked in the past) and the web gui for OTBR fails.

everything goes smoothly until I try to ping the external site according to the directions in the guide.

from each of the Devices.

> ping 64:ff9b::808:808

Done

> 1 packets transmitted, 0 packets received. Packet loss = 100.0%.

I built the OTBR with the option for Ethernet because that is how it is connected to my router and because I previously had bad experiences with the AP setup.

I made a script to execute a few commands on the otbr to help with troubleshooting - this is attached as well as the output.

This is the output of one of my FTD

ipaddr

fd0e:aa2d:48ac:7f4c:0:ff:fe00:c800

fdff:5f8f:720:fa8c:a257:d44a:3a29:252b

fd0e:aa2d:48ac:7f4c:bc37:4984:9c99:5c07

fe80:0:0:0:d86f:bc5d:447d:e69d

oddly, there is no ip address with a mesh local prefix

what can I do to further troubleshoot and obtain routing to my LAN and to the internet?

thanks!
Sincerely,

Mark

PS

==============================================================
I am using otbr
commit b9565b4c44c9ccb413748d82905c8ef741768f57 (HEAD -> main, origin/main, origin/HEAD)

and commissioner

commit f41edbdb7b13103f54bfce6d3423b32e5d6ad5f0 (HEAD -> main, origin/main, origin/HEAD)

and I have two Nordic pca10059 dongles

> version

OPENTHREAD/20191113-01870-gb7751460e; NRF52840; Apr 5 2021 07:43:41

built with this command
make -f examples/Makefile-nrf52840 USB=1 BOOTLOADER=USB JOINER=1 COAP=1 OPENTHREAD_CONFIG_DIAG_ENABLE=1

==============================================================

ip6

otbr_results_ip6.txt

Jonathan Hui

unread,

Apr 7, 2021, 3:47:28 PM4/7/21

to mjkuwp94, openthread-users

Do you have a route configured on the Thread network? You can use the netdata show command to see what routes are configured.

If the network data does not show any default route or external route, you can add a route one of two ways:

You can add an on-mesh prefix with default route:

prefix add fd00:dead:beef:cafe::/64 paros

netdata register

Or you can add an external route specifically for the NAT64 prefix:

route add 64:ff9b::/96 s

netdata register

--

Jonathan Hui

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/61819893-a67e-4cc7-8ac6-f8836630eee2n%40googlegroups.com.

mjkuwp94

unread,

Apr 7, 2021, 4:03:45 PM4/7/21

to openthread-users

is it Normal that I should add routes manually after building the otbr, creating a network and joining the devices? I didn't see this step in the guide. I wonder if this is due to the fact I am using eth0 and I did nothing with the WiFi Access Point Setup section. There isn't any equivalent section for using the Ethernet interface.

Here are some outputs of queries on my otbr. there are routes.

> state

router

Done

> ping 64:ff9b::808:808

Done

> 1 packets transmitted, 0 packets received. Packet loss = 100.0%.

> version

OPENTHREAD/0.01.00; POSIX; Apr 6 2021 20:32:13

Done

> state

router

Done

> netdata show

Prefixes:

fdff:5f8f:720:fa8c::/64 paos med a800

Routes:

2600:6c44:597f:cfcd::/64 s med a800

fd4c:4859:a9c5:0::/64 s med a800

Services:

44970 5d c000 s a800

44970 01 f604b000000e10 s a800

Done

> dataset active

Active Timestamp: 1

Channel: 17

Channel Mask: 0x07fff800

Ext PAN ID: 11112222deadbeef

Mesh Local Prefix: fd0e:aa2d:48ac:7f4c::/64

Master Key: 00112233445566778899aabbccddeeff

Network Name: net2

PAN ID: 0xaa55

PSKc: a04509d13b9bee2ce871ceefbb0de3d8

Security Policy: 672, onrcb

Done

Jonathan Hui

unread,

Apr 7, 2021, 4:16:57 PM4/7/21

to mjkuwp94, openthread-users

Yes, manual configuration is currently expected. We are still working on how NAT64 can be configured automatically.

--

Jonathan Hui

To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/a602e3bf-533a-4408-a315-8ca404ae7b2an%40googlegroups.com.

mjkuwp94

unread,

Apr 7, 2021, 4:46:03 PM4/7/21

to Jonathan Hui, openthread-users

does it mean this guide is wrong, then?

https://openthread.io/guides/border-router/external-commissioning?comm=ot-commissioner

step 8 is "Ping the external internet" and it does not work.

really sorry I do appreciate the help a lot but .... I've been at this project for a long time now trying to do a proof of concept and there always seems to be just 1 thing wrong. : (

the closest I got to good function was the out-of-box Kirale Kibra Border router which seems to be almost the only commercial? solution. but that router would not operate past half a day of tests.

Jonathan Hui

unread,

Apr 7, 2021, 6:13:01 PM4/7/21

to mjkuwp94, openthread-users

If you form the network using the web UI, there is a check box to select whether to advertise a default route.

Using ot-ctl to form the network was added to the guide in a subsequent revision. We should add a note on how to add the default route when doing so.

OpenThread is an open source project and we always welcome contributions from the community. OpenThread has been used successfully in many commercial products - see https://openthread.io#what-products-use-openthread for a listing.