Setting network-manager back to confirmed as I think the case is made
that this is an issue, despite upstream having reservations about
whether network-manager is quite the right place for this particular
setting. Also setting netplan.io in jammy to fix released as 0.105 was
back-ported there
Is this fixed in noble now? No. Is this due to be fixed; I've not heard
anything, but happy to be corrected if this is on a roadmap somewhere?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Is this fixed in Noble?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1951586
Title:
Need option to specify wifi regulatory domain
Status in cloud-init:
Invalid
Status in
Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3926
** Bug watch added: github.com/canonical/cloud-init/issues #3926
https://github.com/canonical/cloud-init/issues/3926
--
You received this bug notification because you are a member of Desktop
Packages, which is
Shoot, guess the wait will be for 20.04 to be updated.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1951586
Title:
Need option to specify wifi regulatory domain
Status in
>Might want to reconsider that position given the latest release of 22.04
>posted on 2023-02-17
>http://cdimage.ubuntu.com/ubuntu/releases/22.04/release/ubuntu-22.04.2-preinstalled-server-
>arm64+raspi.manifest contains netplan.io 0.105-0ubuntu2~22.04.1 which is
>offered by Imager as an
>Imager does not fill in the 'regulatory-domain' field in network-config
because the last time we tried that the existing Ubuntu editions in the
Imager repository did not support the field yet, and reacted badly to
it. As in error'ing out instead of just ignoring.
Might want to reconsider that
>Circled back with the latest server image using rpi-imager to set the
wifi credentials, wifi country does not get populated
Imager does not fill in the 'regulatory-domain' field in network-config
because the last time we tried that the existing Ubuntu editions in the
Imager repository did not
Circled back with the latest server image using rpi-imager to set the wifi
credentials, wifi country does not get populated in network-config but adding
that line in works fine.
https://bugs.launchpad.net/ubuntu/+source/rpi-imager/+bug/2016911
--
You received this bug notification because
I tried the preinstalled desktop image of Ubuntu 23.04 (Lunar Lobster)
Beta last night. It has the same problem, as expected, but it was a bit
tricky to fix it directly on the disk image.
There are two files called 'cmdline.txt', one in each of the disk's two
partitions:
1.
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1951586
** Tags added: iso-testing
--
You received this bug notification because you are a member of Desktop
Packages,
netplan added support for configuring the regulatory domain in kinetic
and it works pretty nicely (it's one of the things I test before
release). However, that's relying on cloud-init to inject the netplan
configuration and that's only on the server images -- it's not a
solution for the
Looking in the root directory of the first partition of the 23.04 beta
image contains 'network-config' think this is a user setting file,
forgot to set this while testing but I was using wired, as the file
contains:
# This file contains a netplan-compatible configuration which cloud-init will
#
Given there doesn't seem much interest in fixing this from the network
manager angle (and there's even a question as to whether that's the
right place to fix this), I'm going to take a leaf out of the RaspiOS
book, and see if I can persuade someone that the installer is the right
place to fix this
> is that having a visible impact for users? like was your computer not
able to connect to some access point?
Yes. I just hit this problem on my new Raspberry Pi 400 with Ubuntu.
The Raspberry Pi OS dated February 21, 2023, based on Debian 11
(bullseye), sets my Wi-Fi region code to Canada
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1951586
Title:
Need option to specify wifi regulatory
This bug was fixed in the package netplan.io - 0.105-0ubuntu1
---
netplan.io (0.105-0ubuntu1) kinetic; urgency=medium
* New upstream release: 0.105
- Add support for VXLAN tunnels (#288), LP: #1764716
- Add support for VRF devices (#285), LP: #1773522
- Add support for
** Changed in: netplan
Status: New => In Progress
** Changed in: netplan
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** Changed in: network-manager
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1951586
Title:
Need option to specify wifi regulatory domain
Thank you for all the background information, Dave!
I've drafted a PR at upstream netplan, to allow setting the regulatory
domain via wpa_supplicant.conf as well as setting it "globally" via 'iw
reg set XX', using a systemd service unit.
https://github.com/canonical/netplan/pull/281
--
You
Sure -- I'll try not to drown them in verbiage :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1951586
Title:
Need option to specify wifi regulatory domain
Status in
@Dave, do you want to maybe add your input directly to the upstream
report?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1951586
Title:
Need option to specify wifi
> It could be maybe added to NetworkManager, if somebody sends a
> patch. But it's not actually clear to me that this is really
> NetworkManager's task. Maybe it is, but what are the arguments for
> that?
I could be glib, and say "because the kernel says so [1]". However, I
suspect that's not a
** Also affects: network-manager via
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/960
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
>> it's apparently never worked for me at home or at various friends
>> houses, and only once worked when I travelled to Germany for a
>> sprint.
> is that having a visible impact for users? like was your computer
> not able to connect to some access point?
Personally, I've never encountered
upstream replied
'''
NetworkManager does currently nothing at all about this.
crda binaries were deprecated, but because there is an alternative
mechanism (wireless-regdb?), isn't it?
It could be maybe added to NetworkManager, if somebody sends a patch. But it's
not actually clear to me that
extra questions, when you wrote
> it's apparently never worked for me at home or at various friends
houses, and only once worked when I travelled to Germany for a sprint.
is that having a visible impact for users? like was your computer not
able to connect to some access point? if that's the
Thanks for the details Dave, there is also a feature request upstream
for network manager on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/960
** Bug watch added:
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #960
I'll take a shot at responding to @seb128's questions:
Why is this a rls issue in the LTS?
===
Prior to jammy, the crda database was in userland, and the crda package
provided a means (via editing /etc/default/crda) to persist the wireless
region across reboots.
The issue has been nominated for network-manager on jammy which put it
on the desktop rls list but it's unclear for us why that is consider a
rls issue in the LTS and what's the intended priority? Could you provide
a bit more explanation of the impact and what do you expect to be
changed?
**
> Should be part of the 'beacon' info.
https://howiwifi.com/2020/07/13/802-11-frame-types-and-formats/ has a
good overview. I discovered this exchange while observing 'on the wire'
with wireshark.
Thanks for the link; lots of useful stuff there!
> > I wondered if perhaps it this only works on
> I wondered if perhaps it this only works on some APs?
That is the impression that I get, the country code info is part of the
management frames transmitted by the AP, could be unsupported, not
configured, or mis-configured.
grep wpa may6.txt
May 6 09:04:57 box wpa_supplicant[810]: wlan0:
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 @
Connection via NetworkManager to AP
2993 May 6 09:55:54 124-u2204-desk NetworkManager[641]:
[1651845354.5017] device (wlp2s0): Activation: starting connection
'181-rpi4-64bit-raspios-LARGE' (9a51eba2-3723-4750-8a72-aa2e4c723140)
2994 May 6 09:55:54 124-u2204-desk NetworkManager[641]:
@jvonau I just came back to this while trawling through my still-open
bug list and had a look at what happens on the desktop. At least on our
Pi desktop images (using NetworkManager), no wifi regulatory domain gets
set at all (at least on my local network). Just in case it made any
difference, I
35 matches
Mail list logo
