© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f291340
demo site
(Get the code!)
I'm not entirely convinced NetworkManager is working correctly this regard? I *was* checking the wifi regulatory domain with "iw reg get" which consistently shows UNSET both globally and for phy#0 under the desktop for Pi images:
$ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
(5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
(5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
(57240 - 63720 @ 2160), (N/A, 0), (N/A)
phy#0
country 99: DFS-UNSET
(2402 - 2482 @ 40), (6, 20), (N/A)
(2474 - 2494 @ 20), (6, 20), (N/A)
(5140 - 5360 @ 160), (6, 20), (N/A)
(5460 - 5860 @ 160), (6, 20), (N/A)
Still, perhaps "iw" doesn't know about changes that wpa_supplicant makes? On a freshly flashed jammy pi desktop card, I get the following output when looking for REGDOM in the wpa_supplicant logs:
$ journalctl -u wpa_supplicant -g REGDOM
-- Boot 732bf3d726d543d
May 09 11:19:54 miss-piggy wpa_supplicant[
The "WORLD" region is presumably consistent with "UNSET" so it doesn't look like NetworkManager or wpa_supplicant is setting things correctly there. I wondered if perhaps it this only works on some APs? So here's the output from my regular development Pi. This also runs the jammy desktop, but it's not a freshly flashed image -- it's been upgraded thru every release since hirsute so it's probably a bit crufty -- but it has travelled with me to various places so it's seen a few different access points (it spends most of its time on ethernet at home though, so the lack of lots of REGDOM changes is not too surprising):
-- Boot 3342ed4b84f14e6
-- Boot d9087ec569c64e2
-- Boot b4c27a9655d747d
-- Boot d431767f6d89494
Sep 29 00:09:43 kermit wpa_supplicant[
-- Boot 345a7579a52147a
Sep 29 09:28:02 kermit wpa_supplicant[
-- Boot 624126fce6cc45a
-- Boot e424d65195804a6
-- Boot 77fb125a0ecc4df
-- Boot da38e67821874b3
-- Boot 02be9377913d488
-- Boot 8a6dc8a10b0f426
-- Boot 85bbc4cfc473439
-- Boot fa07d0686c68401
Jan 14 15:09:22 kermit wpa_supplicant[
-- Boot 9e7e7bf75790439
-- Boot a70d0f388979422
-- Boot bd314e15c8f1415
-- Boot c54489d0e45b431
-- Boot 370a4871b0ec43f
-- Boot 4756c93714f2470
-- Boot 884e307c2a13455
-- Boot bad77d689f714ca
-- Boot 1cf2c96be69748a
-- Boot 09375e4eaaf9414
-- Boot 8fa2bdfb2e6e4ad
-- Boot 6c23de48f7a748d
-- Boot 364f760176b54df
-- Boot ff656412414f4c7
-- Boot ebb1115d58724cf
-- Boot 5c85c03736934ed
-- Boot 6051d9f10827419
-- Boot 4996ddb853a2482
-- Boot 0b7927e93a38434
Feb 14 09:57:26 kermit wpa_supplicant[
-- Boot 08038d28c346496
-- Boot b2c62ed0866d461
Feb 17 01:37:49 kermit wpa_supplicant[
-- Boot 5a2883f8ce074e7
-- Boot ec2157fa46fa48a
-- Boot e2dbc92b2764473
-- Boot ec2157fa46fa48a
-- Boot e2dbc92b2764473
-- Boot a8ef52e6c63949c
Feb 23 10:43:59 kermit wpa_supplicant[
-- Boot 319081b9562a4c2
-- Boot 4d3841cc1dbb490
Feb 26 18:18:07 kermit wpa_supplicant[
-- Boot 8729c7f4e1ae45d
-- Boot 8034051089274a3
-- Boot 8729c7f4e1ae45d
Mar 03 10:07:39 kermit wpa_supplicant[
-- Boot 8034051089274a3
Mar 11 11:20:39 kermit wpa_supplicant[
-- Boot dcd973755091479
-- Boot b0c3f4f9a2d64a8
-- Boot e0fc49c4dc89423
-- Boot 1f2be083fe2e428
-- Boot 76ecf6d5e894408
-- Boot 5fcfbff4b29f4f2
-- Boot 15f5817168b84c3
-- Boot 44d914f21c4444d
-- Boot 238dbb8b6216448
-- Boot 9c66088689b641c
-- Boot d1cc9ac5cd304da
Apr 01 11:31:13 kermit wpa_supplicant[
-- Boot 42f146dbf914494
-- Boot 381cd6a085d34a9
-- Boot 58ca2d99d67641a
Apr 07 22:54:56 kermit wpa_supplicant[
-- Boot 5a5eea05df5f43f
-- Boot 136d1be22bf0465
-- Boot a054dd8d8fe7425
-- Boot 8f7d36b281744f7
-- Boot 890cf4c9b93540b
-- Boot f159c0c4c67b446
-- Boot 59124b1e8b87434
-- Boot cc7d8831649d493
-- Boot 2e9a85dc6919497
-- Boot cf0bca78a10f4d4
-- Boot 95e066d50b9a4f4
-- Boot d6b96bc9d2da48b
-- Boot 6a1885e322674da
-- Boot 265f11639efe4f6
-- Boot 5b96ffce43504e6
-- Boot f8ca9d9135d2495
-- Boot 866d560e03ec426
-- Boot 1a517bf700c14e4
-- Boot e85bdc80cb364b0
-- Boot 65488c22c3c0439
-- Boot c63d9371838e4c9
-- Boot 66e65c4fc40946e
So the upgraded image never sets "GB" either, but it did correctly figure out I'd dragged it into Germany (DE) for the engineering sprint in late February! Still, after that it was back to "WORLD" back in blighty.
Am I looking in the wrong place for REGDOM events? Is there another wpa_supplicant instance that's setting things correctly? Or perhaps there's some setting I'm missing? (although that sounds unlikely given it did correctly figure out Germany).