Thread Network : Border Router configuration

[Valentin]

Hi,

I'm working on a thread network and I have some difficulties to configure the BorderRouter.

I use the BorderRouter V2 rapsberry image from Nordic, I recompile the openthread library with the pre-release Thread reference 2018-09-26 (https://github.com/openthread/openthread/releases/tag/thread-reference-20180926) for the ncp and all works find.

But I want to put a static configuration in the Border Router to configure the PANID, the Channel, the Network Name and the master key.

I try to edit the file /etc/wpantund.conf file with this :

Config:TUN:InterfaceName wpan0
Config:NCP:SocketPath "serial:/dev/ttyACM0,raw,b115200,crtscts=1"
Config:NCP:DriverName spinel
Daemon:SyslogMask "all -debug"

NCP:Channel 20
NCP:TXPower 4

Network:Name Test-Thread
Network:XPANID DEAD00BEEF00CAFE
Network:PANID 0xABCD
Network:Key 00112233445566778899AABBCCDDEEFF

When I reeboot the system, the NCP:state is offline and the thread network is not up. If I restart the wpantund.service (sudo systemctl restart wpantund.service), the thread network restart and it's work. I don't understand why this happen and how can I be sure that the thread network goes up.

I find the file /etc/border_router.conf but it doesn't change thread parameter... I don't understand how this file is using...

Are someone knows how change automaticaly the  thread network parameters from BR after power on?

Thank you,

Valentin

[Edvin]

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