What was the AP equipment? I ran into some issues recently with WiFi 7 and the 6GHz band, where "open" is no longer allowed and a minimum WPA3 is required. It took me a while to realize what was wrong and instead of "open" I could choose "OWE", which stands for Opportunistic Wireless Encryption, which I understand as a kind of handshake that establishes unique keys with the client device to use in connecting to the access point, so it has a similar user experience as "open", but actually encrypts the wireless layer.
-- Russell Senior [email protected] On Mon, Jul 20, 2026 at 9:43 PM Tomas Kuchta <[email protected]> wrote: > > This is an interesting, dare I say exotic, wifi failure mode, at least to > me. > > I was unable to connect to wifi at home today, and also unable to add > anothe AP connection. > > This did not make any sense to me - so, I spent some time looking into it. > I eventually, connected the laptop to ethernet - I asked Claude Fable, if > it could figure it out. > > After some loose ends, me being very, very specific, rejecting bunch of > explanations with data - it comes down to this: > > There is nerby AP, set in BR regulatory domain (Wi-Fi frequencies/channels) > broadcasting BR countey code. This caused my laptop's wifi flapping between > US and BR regulatory domains via 802.11d. So, my wifi saw my US AP picking > its AP object Id , by the time NM got to connect, the wifi card swithed to > BR frequencies/channels and the AP object Id was gone. So, it was timing > issue realy. > > Solution: sudo iw reg set US. > > I do not think that I have enough experience to have figured this out > myself. I checked the diagnosis - journalctl supports it as well as google > search for NM error message: "The access point > /org/freedesktop/NetworkManager/AccessPoint/NNN was not in the scan list." > > I thought, this is worth sharing, not for AI, but as an interesting > networking issue. > > -Tom
