Thread Network : Border Router configuration

RE: Thread Network : Border Router configuration

Valentin — Wed, 20 Mar 2019 13:31:19 GMT

All right, thank you for your support 🙂

RE: Thread Network : Border Router configuration

Edvin — Wed, 20 Mar 2019 11:54:33 GMT

Hello Valentin,

Thank you for sharing!

I am sorry, I am not sure about the way that the border router works, but as you say:

"It doesn't work with a reboot command of the raspberry because the nrf52840 DK NCP keep the power active and the parameter changed in a weird way"

I believe it is because this data is stored in flash. Even power cycling the nRF52840 DK will not change this. The "best" way to reset the behavior is to erase the chip (including the flash pages where the masterkeys are stored) using nrfjprog -e and reprogramming it.

RE: Thread Network : Border Router configuration

Valentin — Wed, 20 Mar 2019 09:16:01 GMT

Hello,

I have tested your solution and it's work ! It doesn't work with a reboot command of the raspberry because the nrf52840 DK NCP keep the power active and the parameter changed in a weird way...

With a reboot, I make a script with a crontab tack at reboot :

#!/bin/bash
wpanctl leave
wpanctl reset
sleep 5
wpanctl form -T 2 GL-BLUEGRioT
wpanctl dataset get-active
wpanctl set dataset:Channel 20
wpanctl set dataset:NetworkName "Test"
wpanctl set dataset:Panid 0xABCD
wpanctl set dataset:ExtendedPanid DEAD00BEEF00CAFE
wpanctl set dataset:Masterkey 00112233445566778899AABBCCDDEEFF
wpanctl set dataset:MeshLocalPrefix "fdde:ad00:beef::64"
wpanctl dataset set-active

This reset my network data, if this can help someone.

Thank you for your response. Do you know what are the difference between the MeshLocalPrefix in the dataset and the thread_on_mesh_prefix in the /etc/border_router.conf ?

Valentin

RE: Thread Network : Border Router configuration

Edvin — Mon, 18 Mar 2019 15:58:28 GMT

Hello,

I tested changing the channel, masterkey (network key) and panid in the border_router.conf file. What I can see is that these changes doesn't take effect until the NCP chip is cleaned (nrfjprog -e) and re-programmed. This is because the network data, once created is stored. So once you have changed the border_router.conf file, plug in a newly erased and reprogrammed with the NCP example, and it should use the settings that are set in border_router.conf.

Best regards,

Edvin