Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Border Router doesn't apply network settings after reboot (TZ-198) #23

Closed
koenvervloesem opened this issue Jul 20, 2023 · 4 comments
Closed

Comments

@koenvervloesem
Copy link

koenvervloesem commented Jul 20, 2023

I flashed this firmware to the Thread Border Router development board and I formed a network in the Web GUI with my own choices for network name, (X)PAN ID, network key, and channel. However, after a reboot the network status in the Web GUI as well as the dataset active command in the CLI show that it has set up a network with the default settings.

The custom network settings are still available after a reboot in the "Form Thread Network" web form, but they aren't applied anymore. Also a dataset commit active command in the CLI and rebooting after applying the changes in the "Form Thread Network" doesn't change this behavior. How do I make the firmware apply my custom network settings from the Web UI?

@github-actions github-actions bot changed the title Border Router doesn't apply network settings after reboot Border Router doesn't apply network settings after reboot (TZ-198) Jul 20, 2023
@gytxxsy
Copy link
Contributor

gytxxsy commented Jul 24, 2023

I flashed this firmware to the Thread Border Router development board and I formed a network in the Web GUI with my own choices for network name, (X)PAN ID, network key, and channel. However, after a reboot the network status in the Web GUI as well as the dataset active command in the CLI show that it has set up a network with the default settings.

The custom network settings are still available after a reboot in the "Form Thread Network" web form, but they aren't applied anymore. Also a dataset commit active command in the CLI and rebooting after applying the changes in the "Form Thread Network" doesn't change this behavior. How do I make the firmware apply my custom network settings from the Web UI?

Currently, this problem occurs if you open OPENTHREAD_BR_AUTO_START via idf.py menuconfig. I would like to know if you use it? If so, you can turn off it as a temporary workaround, and we are actively working on this issue. We will keep you informed when there is an update. Thanks.

@koenvervloesem
Copy link
Author

Thanks for your explanation about the status of this feature. Yes, the OPENTHREAD_BR_AUTO_START option is enabled. Of course by disabling this option, the device doesn't apply any network settings after a reboot, so that's not a useful workaround for me. In the mean time, I've set the dataset via idf.py menuconfig and kept OPENTHREAD_BR_AUTO_START enabled, so the network settings are applied after a reboot.

@chshu
Copy link
Collaborator

chshu commented Jul 25, 2023

Fixed in aa6e6ca

@chshu chshu closed this as completed Jul 25, 2023
@koenvervloesem
Copy link
Author

Thanks for fixing this, I've confirmed it works now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants