You are not logged in.

#1 2022-07-24 07:55:48

0BADC0DE
Member
From: Regnum Utriusque Siciliae
Registered: 2018-02-21
Posts: 176

NetowrkManager doesn't search/connect automatically

I am experiencing this problem since some time now.
On my DE I have configured a couple of SSID to be automatically connected to. One is office's and one is my mobile hotspot. Both are 2.4GHz.
Once logged in, the list of SSIDs doesn't show any of those (while it shows other ones) even after 10 minutis after login.
It starts working only if I disable and re-enable WiFi.

My WiFi device is a "Intel Corporation Wi-Fi 6 AX200 (rev 1a)" (from lspci), networkmanager is 1.38.2-2, I am on KDE/Plasma.
Any hint?

My journalctl says this:

lug 24 09:22:29 Feynman NetworkManager[480]: <info>  [1658647349.8983] NetworkManager (version 1.38.2-2) is starting... (for the first time)
lug 24 09:22:29 Feynman NetworkManager[480]: <info>  [1658647349.8984] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
lug 24 09:22:29 Feynman audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lug 24 09:22:29 Feynman NetworkManager[480]: <info>  [1658647349.9009] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
lug 24 09:22:29 Feynman dbus-daemon[474]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.4' (uid=0 pid=480 comm="/usr/bin/NetworkManager >
lug 24 09:22:30 Feynman NetworkManager[480]: <info>  [1658647350.0979] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.38.2-2/libnm-device-plugin-adsl.so)
lug 24 09:22:30 Feynman NetworkManager[480]: <info>  [1658647350.1007] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.38.2-2/libnm-device-plugin-bluetooth.so)
lug 24 09:22:30 Feynman NetworkManager[480]: <info>  [1658647350.1016] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.38.2-2/libnm-device-plugin-ovs.so)
lug 24 09:22:30 Feynman NetworkManager[480]: <info>  [1658647350.1075] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.38.2-2/libnm-device-plugin-team.so)
lug 24 09:22:30 Feynman NetworkManager[480]: <info>  [1658647350.1087] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.38.2-2/libnm-device-plugin-wifi.so)
lug 24 09:22:30 Feynman NetworkManager[480]: <info>  [1658647350.1092] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.38.2-2/libnm-device-plugin-wwan.so)
lug 24 09:22:30 Feynman dbus-daemon[474]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=480 comm="/usr/bin/Network>
lug 24 09:22:30 Feynman NetworkManager[480]: <info>  [1658647350.1163] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
lug 24 09:22:30 Feynman NetworkManager[480]: <info>  [1658647350.1173] manager: (wlp52s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/2)
lug 24 09:22:30 Feynman audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lug 24 09:22:30 Feynman dbus-daemon[474]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.4' (uid=0 pid=480 comm="/usr/bin/NetworkManager --no-daemon")
lug 24 09:22:30 Feynman NetworkManager[480]: <info>  [1658647350.6680] manager: (p2p-dev-wlp52s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/3)
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4208] manager: NetworkManager state is now CONNECTING
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4386] manager: NetworkManager state is now DISCONNECTED
lug 24 09:22:34 Feynman audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lug 24 09:22:34 Feynman kernel: audit: type=1130 audit(1658647354.450:58): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal>
lug 24 09:22:40 Feynman systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

Offline

#2 2022-07-24 08:07:33

seth
Member
Registered: 2012-09-03
Posts: 30,948

Re: NetowrkManager doesn't search/connect automatically

Don't randomly filter the journal, there's probably something between those lines

lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4208] manager: NetworkManager state is now CONNECTING
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4386] manager: NetworkManager state is now DISCONNECTED

and it might be relevant - as will be the general context of the boot to possibly explain what's going on when the connection fails.
Also don't copy and paste out of the pager (notice the ">" at the end of some lines? Those lines are missing their ends)

sudo journalctl -b | curl -F 'file=@-' 0x0.st

and name the relevant SSIDs (so we can know what connection attempts we need to track)

Offline

#3 2022-07-24 08:32:35

0BADC0DE
Member
From: Regnum Utriusque Siciliae
Registered: 2018-02-21
Posts: 176

Re: NetowrkManager doesn't search/connect automatically

seth wrote:

Don't randomly filter the journal, there's probably something between those lines

lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4208] manager: NetworkManager state is now CONNECTING
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4386] manager: NetworkManager state is now DISCONNECTED

and it might be relevant - as will be the general context of the boot to possibly explain what's going on when the connection fails.
Also don't copy and paste out of the pager (notice the ">" at the end of some lines? Those lines are missing their ends)

sudo journalctl -b | curl -F 'file=@-' 0x0.st

and name the relevant SSIDs (so we can know what connection attempts we need to track)

This is the output of "journalctl -b" piped to a paste service.
The relevant SSID is "Majorana". /etc/NetworkManager/NetworkManager.conf is empty.

I think 09:22 is when it started without connecting.
Then, 10 minutes later, I disabled and re-enabled the WiFi from DE widget and it worked.


Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

Offline

#4 2022-07-24 11:51:53

seth
Member
Registered: 2012-09-03
Posts: 30,948

Re: NetowrkManager doesn't search/connect automatically

lug 24 09:22:29 Feynman NetworkManager[480]: <info>  [1658647349.8983] NetworkManager (version 1.38.2-2) is starting... (for the first time)

NM starts

lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4190] policy: auto-activating connection 'Majorana' (d2c32514-01d0-42dd-9213-96594100ac45)
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4201] device (wlp52s0): Activation: starting connection 'Majorana' (d2c32514-01d0-42dd-9213-96594100ac45)
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4203] device (wlp52s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4208] manager: NetworkManager state is now CONNECTING
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4250] device (wlp52s0): set-hw-addr: reset MAC address to 68:54:5A:14:99:6B (preserve)
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4289] device (wlp52s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4294] device (wlp52s0): Activation: (wifi) access point 'Majorana' has security, but secrets are required.
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4294] device (wlp52s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
lug 24 09:22:34 Feynman NetworkManager[480]: <warn>  [1658647354.4382] device (wlp52s0): no secrets: No agents were available for this request.
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4382] device (wlp52s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')

Tries to connect to Majorana but can't because it doesn't have the PSK and cannot ask for it either.

[code}lug 24 09:24:11 Feynman systemd-logind[477]: New session 2 of user enzo.[/code}
You log in.

lug 24 09:32:24 Feynman NetworkManager[480]: <info>  [1658647944.9284] policy: auto-activating connection 'Majorana' (d2c32514-01d0-42dd-9213-96594100ac45)
lug 24 09:32:24 Feynman NetworkManager[480]: <info>  [1658647944.9290] device (wlp52s0): Activation: starting connection 'Majorana' (d2c32514-01d0-42dd-9213-96594100ac45)
lug 24 09:32:24 Feynman NetworkManager[480]: <info>  [1658647944.9291] device (wlp52s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
lug 24 09:32:24 Feynman NetworkManager[480]: <info>  [1658647944.9296] manager: NetworkManager state is now CONNECTING
lug 24 09:32:24 Feynman NetworkManager[480]: <info>  [1658647944.9332] device (wlp52s0): set-hw-addr: reset MAC address to 68:54:5A:14:99:6B (preserve)
lug 24 09:32:24 Feynman NetworkManager[480]: <info>  [1658647944.9371] device (wlp52s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
lug 24 09:32:24 Feynman NetworkManager[480]: <info>  [1658647944.9372] device (wlp52s0): Activation: (wifi) access point 'Majorana' has security, but secrets are required.
lug 24 09:32:24 Feynman NetworkManager[480]: <info>  [1658647944.9372] device (wlp52s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
lug 24 09:32:24 Feynman NetworkManager[480]: <info>  [1658647944.9449] device (wlp52s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
lug 24 09:32:24 Feynman NetworkManager[480]: <info>  [1658647944.9451] device (wlp52s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
lug 24 09:32:24 Feynman NetworkManager[480]: <info>  [1658647944.9452] device (wlp52s0): Activation: (wifi) connection 'Majorana' has security, and secrets exist.  No new secrets needed.

NM tries to connect to the SSID and succeeds because it has access to your kwallet or wherever the PSK is stored.

lug 24 10:01:06 Feynman wpa_supplicant[580]: wlp52s0: CTRL-EVENT-BEACON-LOSS
lug 24 10:01:06 Feynman wpa_supplicant[580]: wlp52s0: CTRL-EVENT-BEACON-LOSS
lug 24 10:01:06 Feynman wpa_supplicant[580]: wlp52s0: CTRL-EVENT-BEACON-LOSS
lug 24 10:01:06 Feynman wpa_supplicant[580]: wlp52s0: CTRL-EVENT-BEACON-LOSS
lug 24 10:01:06 Feynman wpa_supplicant[580]: wlp52s0: CTRL-EVENT-BEACON-LOSS
lug 24 10:01:06 Feynman wpa_supplicant[580]: wlp52s0: CTRL-EVENT-DISCONNECTED bssid=fe:4a:b1:f8:2c:ce reason=4 locally_generated=1
lug 24 10:01:06 Feynman NetworkManager[480]: <info>  [1658649666.8032] device (wlp52s0): supplicant interface state: completed -> disconnected
lug 24 10:01:06 Feynman NetworkManager[480]: <info>  [1658649666.8033] device (p2p-dev-wlp52s0): supplicant management interface state: completed -> disconnected
lug 24 10:01:06 Feynman NetworkManager[480]: <info>  [1658649666.8976] device (wlp52s0): supplicant interface state: disconnected -> scanning
lug 24 10:01:06 Feynman NetworkManager[480]: <info>  [1658649666.8977] device (p2p-dev-wlp52s0): supplicant management interface state: disconnected -> scanning
lug 24 10:01:09 Feynman wpa_supplicant[580]: wlp52s0: SME: Trying to authenticate with fe:4a:b1:f8:2c:ce (SSID='Majorana' freq=2412 MHz)
lug 24 10:01:09 Feynman kernel: wlp52s0: authenticate with fe:4a:b1:f8:2c:ce
lug 24 10:01:09 Feynman kernel: wlp52s0: 80 MHz not supported, disabling VHT
lug 24 10:01:09 Feynman wpa_supplicant[580]: wlp52s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
lug 24 10:01:09 Feynman kernel: wlp52s0: send auth to fe:4a:b1:f8:2c:ce (try 1/3)
lug 24 10:01:09 Feynman NetworkManager[480]: <info>  [1658649669.5557] device (wlp52s0): supplicant interface state: scanning -> authenticating
lug 24 10:01:09 Feynman NetworkManager[480]: <info>  [1658649669.5558] device (p2p-dev-wlp52s0): supplicant management interface state: scanning -> authenticating
lug 24 10:01:09 Feynman kernel: wlp52s0: send auth to fe:4a:b1:f8:2c:ce (try 2/3)
lug 24 10:01:09 Feynman kernel: wlp52s0: send auth to fe:4a:b1:f8:2c:ce (try 3/3)
lug 24 10:01:09 Feynman kernel: wlp52s0: authentication with fe:4a:b1:f8:2c:ce timed out
lug 24 10:01:09 Feynman NetworkManager[480]: <info>  [1658649669.9298] device (wlp52s0): supplicant interface state: authenticating -> disconnected
lug 24 10:01:09 Feynman NetworkManager[480]: <info>  [1658649669.9298] device (p2p-dev-wlp52s0): supplicant management interface state: authenticating -> disconnected
lug 24 10:01:10 Feynman NetworkManager[480]: <info>  [1658649670.4313] device (wlp52s0): supplicant interface state: disconnected -> scanning
lug 24 10:01:10 Feynman NetworkManager[480]: <info>  [1658649670.4313] device (p2p-dev-wlp52s0): supplicant management interface state: disconnected -> scanning
lug 24 10:01:21 Feynman NetworkManager[480]: <warn>  [1658649681.9811] device (wlp52s0): link timed out.
lug 24 10:01:21 Feynman NetworkManager[480]: <info>  [1658649681.9817] device (wlp52s0): state change: activated -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
lug 24 10:01:21 Feynman NetworkManager[480]: <info>  [1658649681.9823] manager: NetworkManager state is now DISCONNECTED
lug 24 10:01:21 Feynman avahi-daemon[470]: Interface wlp52s0.IPv4 no longer relevant for mDNS.
lug 24 10:01:21 Feynman avahi-daemon[470]: Leaving mDNS multicast group on interface wlp52s0.IPv4 with address 192.168.33.46.
lug 24 10:01:21 Feynman avahi-daemon[470]: Withdrawing address record for 192.168.33.46 on wlp52s0.
lug 24 10:01:21 Feynman NetworkManager[480]: <info>  [1658649681.9863] device (wlp52s0): set-hw-addr: set MAC address to 6A:48:CA:83:2A:24 (scanning)
lug 24 10:01:21 Feynman avahi-daemon[470]: Joining mDNS multicast group on interface wlp52s0.IPv4 with address 192.168.33.46.
lug 24 10:01:21 Feynman avahi-daemon[470]: New relevant interface wlp52s0.IPv4 for mDNS.
lug 24 10:01:21 Feynman avahi-daemon[470]: Registering new address record for 192.168.33.46 on wlp52s0.IPv4.
lug 24 10:01:21 Feynman NetworkManager[480]: <warn>  [1658649681.9904] device (wlp52s0): Activation: failed for connection 'Majorana'

After ~30 minutes you lose the Majorana signal (moving away from the AP?)

lug 24 10:15:35 Feynman NetworkManager[480]: <info>  [1658650535.9851] device (wlp52s0): set-hw-addr: set MAC address to C6:E6:9F:12:E2:EF (scanning)
lug 24 10:16:05 Feynman NetworkManager[480]: <info>  [1658650565.7467] policy: auto-activating connection 'Majorana' (d2c32514-01d0-42dd-9213-96594100ac45)
lug 24 10:16:05 Feynman NetworkManager[480]: <info>  [1658650565.7476] device (wlp52s0): Activation: starting connection 'Majorana' (d2c32514-01d0-42dd-9213-96594100ac45)
lug 24 10:16:05 Feynman NetworkManager[480]: <info>  [1658650565.7480] device (wlp52s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
lug 24 10:16:05 Feynman NetworkManager[480]: <info>  [1658650565.7486] manager: NetworkManager state is now CONNECTING
lug 24 10:16:05 Feynman NetworkManager[480]: <info>  [1658650565.7527] device (wlp52s0): set-hw-addr: reset MAC address to 68:54:5A:14:99:6B (preserve)
lug 24 10:16:05 Feynman NetworkManager[480]: <info>  [1658650565.7569] device (wlp52s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
lug 24 10:16:05 Feynman NetworkManager[480]: <info>  [1658650565.7571] device (wlp52s0): Activation: (wifi) access point 'Majorana' has security, but secrets are required.
lug 24 10:16:05 Feynman NetworkManager[480]: <info>  [1658650565.7571] device (wlp52s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
lug 24 10:16:05 Feynman NetworkManager[480]: <info>  [1658650565.7659] device (wlp52s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
lug 24 10:16:05 Feynman NetworkManager[480]: <info>  [1658650565.7660] device (wlp52s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
lug 24 10:16:05 Feynman NetworkManager[480]: <info>  [1658650565.7661] device (wlp52s0): Activation: (wifi) connection 'Majorana' has security, and secrets exist.  No new secrets needed.

~15 minutes later you reconnect (wait, did you take your notebook to the toilet? wink)

https://wiki.archlinux.org/title/Networ … et_on_boot
I'm gonna say you did 3 but not 4?

Offline

#5 2022-07-25 08:04:16

0BADC0DE
Member
From: Regnum Utriusque Siciliae
Registered: 2018-02-21
Posts: 176

Re: NetowrkManager doesn't search/connect automatically

This is weird. That SSID is configured with:
- Connect automatically with priority (0)
- All users may connect to the this network

This should mean, AFAIK, that the WPA2 key is stored somewhere in a file (in/etc) and that it should not need KDE wallet to be unlocked (as it happenss for all the other other SSIDs of mine).

In any case, I am not talking about the ability/unability to connect to the SSID, but rather the fact that the SSID is not shown in the list of the available ones until I restart the WiFi subsystem,
Thus it is not connected automatically.


Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

Offline

#6 2022-07-25 08:09:26

seth
Member
Registered: 2012-09-03
Posts: 30,948

Re: NetowrkManager doesn't search/connect automatically

The wiki explicitly wrote:

Additionally, ensure that under "Wi-Fi Security", "Store password for all users (not encrypted)" is selected

Offline

#7 2022-07-25 08:11:40

0BADC0DE
Member
From: Regnum Utriusque Siciliae
Registered: 2018-02-21
Posts: 176

Re: NetowrkManager doesn't search/connect automatically

seth wrote:
The wiki explicitly wrote:

Additionally, ensure that under "Wi-Fi Security", "Store password for all users (not encrypted)" is selected

Noted.

0BADC0DE wrote:

In any case, I am not talking about the ability/unability to connect to the SSID, but rather the fact that the SSID is not shown in the list of the available ones until I restart the WiFi subsystem,
Thus it is not connected automatically.

I am still not seeing the SSID until I restart the WiFi subsystem...

Last edited by 0BADC0DE (2022-07-25 08:14:42)


Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

Offline

#8 2022-07-25 08:23:17

seth
Member
Registered: 2012-09-03
Posts: 30,948

Re: NetowrkManager doesn't search/connect automatically

Not sure about "restart the WiFi subsystem", but I'd be less than surprised if NM simply masks a failing service to not spoil the radio w/ futile connection attempts.
I suppose you'll not find that problem if you either disable or correctly configure the global connection to the SSID.

Offline

#9 2022-07-25 08:34:36

0BADC0DE
Member
From: Regnum Utriusque Siciliae
Registered: 2018-02-21
Posts: 176

Re: NetowrkManager doesn't search/connect automatically

seth wrote:

Not sure about "restart the WiFi subsystem", but I'd be less than surprised if NM simply masks a failing service to not spoil the radio w/ futile connection attempts.

I still think that an unsuccessfully connected SSID should show up in the list at least for a new manual attempt. Shouldn't it?
After all, that is supposed to be a list of "whatever SSID  is within reach", no matter the availablity of a key for it, IMHO.

seth wrote:

I suppose you'll not find that problem if you either disable or correctly configure the global connection to the SSID.

The global connection to that SSID is configured correctly according to the linked wiki page.
The only thing I can think of is that that SSID used to be "for this user only" with the secret stored into KWallet.
Then I moved it to be "for all users". This should haven't changed the visibiity in the listo of available SSIDs anyway.

I think this is a bug in NM or in the distributed package.
Will try with upstream bug reporting.

Thanks for your great help so far.

Last edited by 0BADC0DE (2022-07-25 08:37:58)


Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

Offline

#10 2022-07-25 08:48:50

seth
Member
Registered: 2012-09-03
Posts: 30,948

Re: NetowrkManager doesn't search/connect automatically

You wrote:

The global connection to that SSID is configured correctly according to the linked wiki page.
The only thing I can think of is that that SSID used to be "for this user only" with the secret stored into KWallet.
Then I moved it to be "for all users".

And you previously wrote:

That SSID is configured with:
- Connect automatically with priority (0)
- All users may connect to the this network

The wiki wrote:

Additionally, ensure that under "Wi-Fi Security", "Store password for all users (not encrypted)" is selected

NetworkManager wrote:

lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4294] device (wlp52s0): Activation: (wifi) access point 'Majorana' has security, but secrets are required.
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4294] device (wlp52s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
lug 24 09:22:34 Feynman NetworkManager[480]: <warn>  [1658647354.4382] device (wlp52s0): no secrets: No agents were available for this request.
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4382] device (wlp52s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')

Offline

#11 2022-07-25 09:22:04

0BADC0DE
Member
From: Regnum Utriusque Siciliae
Registered: 2018-02-21
Posts: 176

Re: NetowrkManager doesn't search/connect automatically

seth wrote:
You wrote:

The global connection to that SSID is configured correctly according to the linked wiki page.
The only thing I can think of is that that SSID used to be "for this user only" with the secret stored into KWallet.
Then I moved it to be "for all users".

And you previously wrote:

That SSID is configured with:
- Connect automatically with priority (0)
- All users may connect to the this network

The wiki wrote:

Additionally, ensure that under "Wi-Fi Security", "Store password for all users (not encrypted)" is selected

NetworkManager wrote:

lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4294] device (wlp52s0): Activation: (wifi) access point 'Majorana' has security, but secrets are required.
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4294] device (wlp52s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
lug 24 09:22:34 Feynman NetworkManager[480]: <warn>  [1658647354.4382] device (wlp52s0): no secrets: No agents were available for this request.
lug 24 09:22:34 Feynman NetworkManager[480]: <info>  [1658647354.4382] device (wlp52s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')

Exactly: that SSID is configured like that. Previously it was configured with encrypted key.

The main problem is not about connecting but rather about listing all SSIDs with reach.
If the system cannot connect becasue of unavailable key, I could still hit the "Connect" button.


Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

Offline

#12 2022-07-25 12:34:41

seth
Member
Registered: 2012-09-03
Posts: 30,948

Re: NetowrkManager doesn't search/connect automatically

Exactly: that SSID is configured like that. Previously it was configured with encrypted key.

The initial pre-login connection should then no longer fail? So how would you then still face the original problem of not being able to connect to that AP after the login when the connection has already been established…???

Offline

#13 2022-07-25 14:10:42

0BADC0DE
Member
From: Regnum Utriusque Siciliae
Registered: 2018-02-21
Posts: 176

Re: NetowrkManager doesn't search/connect automatically

seth wrote:

Exactly: that SSID is configured like that. Previously it was configured with encrypted key.

The initial pre-login connection should then no longer fail? So how would you then still face the original problem of not being able to connect to that AP after the login when the connection has already been established…???

The situation on my system is exactly as described.
I have a non-hidden SSID with a valid WPA2 PSK stored in a system file, but NM doesn't show it until I reset the wifi subsystem.
If I had an answer I would be posting it here. But unluckily, due to my ignorance, I haven't got any.

By default all SSIDs are unauthenticated either because the provided credential is "not good" or because there is no available credential at all.
In either case, if the SSID is not hidden, it needs to show up as long as it is picked up by wpa_supplicant.
Where is my mistake here? Am I wishful thinking?
Which is not true. So either NM or wpa_suplicant are refusing to lost my SSID.

Last edited by 0BADC0DE (2022-07-25 14:11:22)


Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.

Offline

#14 2022-07-25 14:13:50

seth
Member
Registered: 2012-09-03
Posts: 30,948

Re: NetowrkManager doesn't search/connect automatically

I have a non-hidden SSID with a valid WPA2 PSK stored in a system file

To avoid talking past each other, please post an updated journal.
Also use nmcli to show the connections to not be subject to some overzealous GUI.

Offline

Board footer

Powered by FluxBB