Wi-Fi auto connect after boot

Help
23

Which I guess the network is not. There might be some clue in the syslog, either from the net server or from wpa_supplicant.

I don’t understand network code, but it seems one possibility to get no auth is a problem getting the network, like I don’t know, maybe the scan has not finished or something? Another one might be that it’s stated in the wireless_networks file humdinger pointed to. While I only have a list of network entries with SSID, it seems one can have among other things authentication entries that would set the auth mode used.

Please do not delete the keystore_database, it may have many other things. You can explore and edit it with the keystore command:

~> keystore list keyrings
keyring: "Calendar"
keyring: "Master"
keyring: "wpa_supplicant"
~> keystore list passwords wpa_supplicant
password key:
        purpose: network
        identifier: [and some more data, including the passwords]
2 Likes
24

Used the keystore cli already pretty mutch when trying out daily builds for NeoChat, the main app in the depot stores it in “NeoChat”, with keystore remove password neochat I can remove it from the list and launch a binary build with kde-builder to test it out.

EDIT: the cmd above does not remove the password for NeoChat (case sensitive).

25

Nothing I do seems to create the “/boot/system/settings/network/wireless_network" file.

Can one of y’all post the (redacted, obs) content of yours?

26

Mine just has a list network SSID lines with the ones I have connected to and saved:

network MYHOME
network MYUNCLES
1 Like
27

It’s just a one liner (I didn’t need to add it manually, it was already there):

network <SSID>

Yes, there is:

BMessage(0x0) {
        format = uint32(0x1 or 1)
        keyrings[0] = BMessage(0x0) {
                noData = bool(true)
                hasUnlockKey = bool(false)
                name = string("Master", 7 bytes)
        }
        keyrings[1] = BMessage(0x0) {
                data = (type = 'RAWT')(size = 963)
                hasUnlockKey = bool(false)
                name = string("wpa_supplicant", 15 bytes)
        }
}

None of the above helps though. It won’t auto connect because it assumes “Open” authentication.

28

Well, that didn’t go well. :slight_smile:

I created the file as described and rebooted.

The wireless did not try to autoconnect, and when I manually told it to it claimed to be connected but did not manage to get a config from DHCP.

I deleted the file and it reconnected and got an IP from DHCP immediately, but couldn’t ping anything.

Rebooting again (without the file) put it back to normal.

That sequence of events makes no sense at all. :slight_smile:

29

Hi everyone,

​A few days ago, I installed Beta 5 on an old HP laptop equipped with an RTL8188EE wireless card. I noticed that on boot, it wouldn’t automatically connect to my saved network.

​While troubleshooting, I checked the /boot/system/settings/network/wireless_networks file, and the network name was listed there correctly.

​I also checked the keystore using the following command:

keystore list passwords wpa_supplicant

Both the network SSID and the password appeared to be saved properly.

​Then, I noticed that my SSID consists of two words separated by a space. I decided to modify the network name inside the /boot/system/settings/network/wireless_networks file by adding quotes around it, like this:

​network “MY SSID”

​…and now everything works perfectly! Just wanted to share this in case anyone else bumps into the same issue with SSIDs containing spaces.

4 Likes
30

Mine doesn’t have spaces, but it does have some other special characters so I’ll try this on my next reboot. Thanks for the suggestion.

EDIT: sadly, still no automatic connect.