yahoo-eng-team team mailing list archive

[Dave Jones <1951586@xxxxxxxxxxxxxxxxxx>]

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 quite a while ago now and the current (22.04.3) image
should support setting this at first-boot. Setting kinetic to won't fix
(as it's EOL).

** Changed in: network-manager (Ubuntu Kinetic)
       Status: Incomplete => Won't Fix

** Changed in: network-manager (Ubuntu Jammy)
       Status: Incomplete => Confirmed

** Changed in: network-manager (Ubuntu)
       Status: Incomplete => Confirmed

** Changed in: netplan.io (Ubuntu Jammy)
       Status: Triaged => Fix Released

** Changed in: netplan
     Assignee: Lukas Märdian (slyon) => (unassigned)

** Also affects: network-manager (Ubuntu Lunar)
   Importance: Undecided
       Status: New

** Also affects: netplan.io (Ubuntu Lunar)
   Importance: Undecided
       Status: New

** Also affects: network-manager (Ubuntu Noble)
   Importance: Low
       Status: Confirmed

** Also affects: netplan.io (Ubuntu Noble)
   Importance: Medium
       Status: Fix Released

** Also affects: network-manager (Ubuntu Mantic)
   Importance: Undecided
       Status: New

** Also affects: netplan.io (Ubuntu Mantic)
   Importance: Undecided
       Status: New

** Changed in: netplan.io (Ubuntu Lunar)
       Status: New => Fix Released

** Changed in: netplan.io (Ubuntu Mantic)
       Status: New => Fix Released

** Changed in: network-manager (Ubuntu Lunar)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu Lunar)
       Status: New => Confirmed

** Changed in: network-manager (Ubuntu Mantic)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu Mantic)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1951586

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  Fix Released
Status in NetworkManager:
  New
Status in netplan.io package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Confirmed
Status in netplan.io source package in Jammy:
  Fix Released
Status in network-manager source package in Jammy:
  Confirmed
Status in netplan.io source package in Kinetic:
  Fix Released
Status in network-manager source package in Kinetic:
  Won't Fix
Status in netplan.io source package in Lunar:
  Fix Released
Status in network-manager source package in Lunar:
  Confirmed
Status in netplan.io source package in Mantic:
  Fix Released
Status in network-manager source package in Mantic:
  Confirmed
Status in netplan.io source package in Noble:
  Fix Released
Status in network-manager source package in Noble:
  Confirmed

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions