RG35XX H
WiFi is on at boot even if I’ve disconnected before reboot.
I’ve tried deleting profile, changing password, and combinations of those and disconnecting and then exiting menu before shutdown or reboot; these also in combination with turning SSH off/on.
I confirmed that it really is connecting via SSH’ing in.
Try removing /etc/wpa_supplicant.conf (in dingux commander, terminal, ssh, whatever) then rebooting
I deleted it, wiped the profile again, and the yellow WiFi icon appears again.
When I deleted the /etc/wpa_supplicant.conf file and rebooted without messing with the profile, it showed up yellow, but did not actually connect.
Then, I deleted the profile without changing the settings, and I rebooted once more; then, it really did connect automatically.
I’m interested in a way to clear the settings of the wifi module so that it isn’t actively connected to a network when the user explicitly doesn’t want the device to use the last saved/working settings, regardless of the power footprint.
I realize the security implications of this are minimal if you don’t open up web services and ports on the device, but it would be good to have the device in a state where it doesn’t automatically connect.
does the task toolkit script Restore Network Configuration not work? I thought that wiped everything. I made a profile of my current network settings, then ran that script, then rebooted and it was not connected to the network anymore.
Task Toolkit to the rescue again, would it be worth it to integrate what the script does into the Wi-fi menu for the disconnect option?
We could probably add a “Auto Connect” option that will connect the device but ensure connection information (like /etc/wpa_supplicant) is purged on startup.
the other day my brick would not connect to wifi until I purged the /etc/wpa_supplicant.conf file
The brick has seemingly terrible Wi-Fi support. Only has 2.4GHz connections, in saying that I had to move my router closer to my workstation and haven’t had issues since.
Not the best solution I know but I haven’t had issues with reconnections on startup since.
I should have noted sooner that base PIXIE didn’t have this issue. It would remember and maintain persistence of the last state of being connected or not on reboot.