Closed glfejer closed 4 years ago
Does captived
issue a SIGHUP
to connmand
after updating the wifi config files?
EDIT: Yes it does, via this command.
The connmand
service should not be killed by the SIGHUP
. I'd added code to just reload the configs in response to that signal. Perhaps that code got lost in the switch to the latest Buildroot?
EDIT: Yep, those patches will install for connman 1.36: https://github.com/xaptum/xaptum-buildroot/tree/master/buildroot-external-xaptum/patches/connman/1.36
But we're now on 1.37. Need to migrate those patches to 1.37.
I'll prep an updated patch for xaptum-buildroot
. @glfejer Then you can give a test.
To reproduce: router is connected to MakeOffices wifi:
New,
broken.json
configuration is:Update configuration:
Router card acknowledges the change. Repeated calls to status shows no change in connected network.
Router card shows that connman has exited:
Restarting connman with
systemctl start connman
causes router to disconnect from previous network, but doesn't connect to recovery network. Recovery network is visible when issuingconnmanctl services
When a reboot issued via
curl
prior to restarting connman, the reboot succeeds and router card connects to recovery network. After connman is restarted, a reboot must be issued on the board.