Bug#972366: marked as done (debian-installer: It may be illegal not to set wireless regulatory domain)
Your message dated Tue, 20 Oct 2020 05:34:36 +0900 (JST)
with message-id <20201020.053436.1393092694108154006.ryutaroh@ict.e.titech.ac.jp>
and subject line Re: Bug#972366: debian-installer: It may be illegal not to set wireless regulatory domain
has caused the Debian Bug report #972366,
regarding debian-installer: It may be illegal not to set wireless regulatory domain
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
972366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972366
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: 20200314
Severity: important
Dear Maintainer,
According to
https://wireless.wiki.kernel.org/en/developers/regulatory
when a wireless interface is used by Linux, wireless regulatory
domain must be set to comply the laws.
But current installer does not seem to set it.
As far as I know, it can be set by
REGDOMAIN in /etc/default/crda of crda package, or
country in /etc/wpa_cupplicant/wpa_supplicant.conf
There seems no way to set wireless reg. domain by ifupdown.
Worse, NetworkManager seems to overwrite it, as
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1232928
https://bugzilla.gnome.org/show_bug.cgi?id=720331
Best regards, Ryutaroh Matsumoto
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.8.0-2-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Ben,
Thank you for your explanation.
I misunderstood and this should not be considered as a bug.
Best regards, Ryutaroh
From: Ben Hutchings <ben@decadent.org.uk>
Subject: Re: Bug#972366: debian-installer: It may be illegal not to set wireless regulatory domain
Date: Mon, 19 Oct 2020 15:44:26 +0100
> Control: tag -1 moreinfo
>
> On Sat, 2020-10-17 at 09:36 +0900, Ryutaroh Matsumoto wrote:
>> Package: debian-installer
>> Version: 20200314
>> Severity: important
>>
>> Dear Maintainer,
>>
>> According to
>> https://wireless.wiki.kernel.org/en/developers/regulatory
>>
>> when a wireless interface is used by Linux, wireless regulatory
>> domain must be set to comply the laws.
>> But current installer does not seem to set it.
> [...]
>
> In most cases, this should not be necessary. A regulatory domain is
> defined in the NVRAM of the local wireless interface, and access points
> will also include this information in their beacons.
>
> In case you use wireless hardware that was intended for use in a
> different regulatory area, and you configure it as an AP, then you
> should set the regulatory domain. But I don't think it makes sense for
> the installer to try to set this - it only ever configures wifi
> interfaces for infrastructure mode.
>
> Am I missing something?
>
> Ben.
>
> --
> Ben Hutchings
> Anthony's Law of Force: Don't force it, get a larger hammer.
>
>
--- End Message ---
Reply to: