You should report this to the FCC if you can find the AP, since it's illegal for someone in the US to set a wifi unit to any regulatory domain than the US.
I definitely would find the owner of the wifi unit and inform them, and if they were resistant to fixing it, I would have the FCC explain it to them. Ted -----Original Message----- From: PLUG <[email protected]> On Behalf Of Tomas Kuchta Sent: Monday, July 20, 2026 9:43 PM To: Portland Linux/Unix Group <[email protected]> Subject: [PLUG] Unable to connect to wifi due to 802.11d - flapping wifi regulatory domain 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
