Thread Border Router networking fail

[Rick]

Hello Nordic Taam:

I follow the WEB steps below

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_tz_v4.1.0%2Fthread_ot_performance_measurement.html

Software Development Kit > nRF5 SDK for Thread and Zigbee v4.1.0 > Thread > Thread tools > Thread Border Router

nRF52840 DK Version：nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\ncp\ftd\uart\hex

Raspberry Pi 3 Version：RaspPi_OT_Border_Router_Demo_v4.1.0-1.alpha

Use nRF52840 DK UART connect Raspberry Pi 3 to get the following information

wpan0 => [
"NCP:State" => "associating"
"Daemon:Enabled" => true
"NCP:Version" => "OPENTHREAD/20191113-00534-gc6a258e3; NRF52840; Apr 5 2020 21:51:18"
"Daemon:Version" => "0.08.00d (; Apr 21 2020 19:11:43)"
"Config:NCP:DriverName" => "spinel"
"NCP:HardwareAddress" => [F4CE363EC3C45B0E]
]

pi@raspberrypi:~ $ sudo wpanctl status
wpan0 => [
"NCP:State" => "uninitialized"
"Daemon:Enabled" => true
"NCP:Version" => ""
"Daemon:Version" => "0.08.00d (; Apr 21 2020 19:11:43)"
"Config:NCP:DriverName" => "spinel"
"NCP:HardwareAddress" => [F4CE363EC3C45B0E]
]

If I have the wrong steps or have not completed, please give me some pointers, thank you.

Also, can you teach me how to set up the Thread Border Router successfully on Raspberry Pi 3?

Best Regards

Rick.

[Jørgen Holmefjord]

Hi,

The instructions on Thread Border Router is the latest and should be correct. It also looks like you are using the correct versions of the firmware and border router image. 

I have tested this multiple times before, and have not had any issues with getting the network up and running.

Are you using a revision 1 DK or later? Did you have the DK connected to the RPi before you booted it? Did you run 'erase all' command on the DK before flashing the NCP FW? You did not run any other commands on the border router prior to the "sudo wpanctl status" command?

If nothing works, I would suggest that you start over and flash the DK and border router image again to the devices to see if that solves any issues.

Best regards,
Jørgen

[Rick]

Hi Jørgen:

How are you today!

Is there any update?

Pls kindly help advise how to solve it?

Best Regards,

Rick.

[Jørgen Holmefjord]

If you have a WAN prefix of 64, you will not be able to make the router set a 56 prefix for the LAN address, the WAN subnet needs to be large in order to provide larger subnets.

When I have tested this, I was assigned a 48 prefix address from my ISP, and was able to get a 56 subnet to the Border Router.

[Rick]

Hi Jørgen

This is my Router Setting, Pls looking it and check the green block it, this you say WAN prefix of 64?
So I need ISP support WAN prefix of 48?

[Jørgen Holmefjord]

Yes, you need ISP to provide you with a WAN prefix same or lower than the one you want assigned to the subnet. If you want /56 subnet to border router/LAN prefix, you need at least /56 prefix from ISP.

[Rick]

OK, I go to check ISP provide WAN, thanks. 

[Rick]

Hi Jørgen

How are you today!
now I need to test IPv6 /56 prefix from OpenWRT.
Pls kindly help advise any support list for OpenWRT Router and support version for OpenWRT?
Asus Router or other?

Best Regards,
Rick.

[Jørgen Holmefjord]

Hi Rick,

Unfortunately, this is not something we can assist with. Router configuration is way outside of our area of expertise, I'm sure you can find some help with this on OpenWRT forum or similar.

I only tested this briefly a few years ago with a Netgear WNR3500v2/RangeMax N300 router. I do not remember exactly which firmware I used.

Best regards,
Jørgen