In our company, we deliver preloaded Edge-Devices with the BalenaOS. However we don’t know the IP-Settings of the customers, so we created a file called “resin-static-net5” in the system-connections folder on the boot partition of the flash thumb drive. Then we wrote a script that connects to NetworkManager DBUS API and let the customer change the Settings of the resin-static-net5 file (the interface is called net5) with the script. We tested it and it worked. we were able to change the settings from auto/dhcp to manual/static ip. After reboot the changed settings were still available.
However we tested it last week, and out of a sudden it is not working anymore. We are able to chage the settings over DBUS but when we reboot the device the settings are now lost.
in the Documentation the following is written:
"On device boot, the files in
resin-boot/system-connections are copied into
So after i changed my settings i checked the files.
/etc/NetworkManager/system-connections/resin-static-net5 AND /resin-boot/system-connections/resin-static-net5 have been changed.
/mnt/boot/system-connections/resin-static-net5 is still the old one that we copied to the flash thumb drive.
After reboot all files are being reset to the old one that is on /mnt/boot/system-connections/resin-static-net5.
So my questions are:
- why did it work in the past, but now it is not working? If i understand the Documentation correct this is not the intended behavior.
- is there currently a solution for this problem? how can one achieve that the changed network settings with DBUS are also present after a device reboot?
Thanks a lot in advance.
currently we are using balenaOS 2.58.6+rev1 dev image