From seth.forshee at canonical.com  Tue Jul  6 08:45:01 2021
From: seth.forshee at canonical.com (Seth Forshee)
Date: Tue, 6 Jul 2021 10:45:01 -0500
Subject: [wireless-regdb] [PATCH] wireless-regdb: recent FCC report and
 order allows 5850-5895 immediately
In-Reply-To: <CAPuHQ=GbacSTgyimkJtx1FXp319Df=LdrPQZ6ZDnPQ_JVXueKw@mail.gmail.com>
References: <a79286b90cdfdee3a83397008c0f7b6d67bc7f69.1607035229.git.b.K.il.h.u+tigbuh@gmail.com>
 <YL+RDtGatz/ybG+M@ubuntu-x1>
 <CAPuHQ=GbacSTgyimkJtx1FXp319Df=LdrPQZ6ZDnPQ_JVXueKw@mail.gmail.com>
Message-ID: <YOR6fRX+RkpjWECF@ubuntu-x1>

I've been on vacation; sorry for the delay.

On Wed, Jun 30, 2021 at 05:17:37PM +0200, b.K.il.h.u+tigbuh at gmail.com wrote:
> > On Tue, Jun 8, 2021 at 5:47 PM Seth Forshee <seth.forshee at canonical.com> wrote:
> > I think we concluded previously that both 5730-5850 and 5850-5895 should
> > have a max bandwidth of 160 MHz to permit use of 160 MHz across these
> > channels.
> >
> 
> Yes.
> 
> > We also discussed using NO-IR for 5850-5895. The regulations forbid
> > active scans, and PMTP-ONLY does not prevent them. NO-IR appears to be
> > the only option which conforms to this restriction, though that will
> > also block running an AP in this range.
> >
> 
> So we would not be able to operate an OpenWrt or other Linux-based AP,
> while other vendors would be allowed to do this? How is this
> acceptable? How does this help in liberating the band?

We're allowing clients which use the rules in the db to connect to APs
in the band. We may be able to get APs supported later on by getting
changes to break up passive-scan and no-IR. But with what we have to
work with right now, and based on my interpretation of the rules, I
think this is the best we can do currently.

> > I also read the max EIRP for clients as 30 dBm without any TPC
> > requirement. Did I overlook something which limits the EIRP to 27 dBm?
> >
> 
> The 27 dBm EIRP is needed for 20 MHz operation due to spectral density
> requirements. Is my information correct that regdb has no notion of
> specifying a separate limit for spectral density? (If it did, we might
> be able to double the EIRP for 2.4GHz of 10MHz channels)
> 
> I have summarized the reasoning in a comment of the original patch,
> but let me cite it here then (copied from the more recent link you
> have now given):
> 
> > "(iii) For client devices operating under the control of an indoor access point in the 5.850-5.895 GHz band, the maximum power spectral density must not exceed 14 dBm e.i.r.p. in any 1-megahertz band, and the maximum e.i.r.p. over the frequency band of operation must not exceed 30 dBm."
> > "the Commission limited indoor access point EIRP spectral density to 20 dBm/MHz with a maximum EIRP of 36 dBm over the bandwidth of operation (e.g., 33 dBm/20 MHz and 36 dBm/40 MHz)"
> > "To keep the potential for causing harmful interference low, the Commission required client devices to operate under the control of an access point, and limited client device's power spectral density and maximum transmit power to 6 dB below the power permitted for the access point."

Ah, thanks, I had forgotten about this.

Seth


From seth.forshee at canonical.com  Tue Jul  6 08:51:42 2021
From: seth.forshee at canonical.com (Seth Forshee)
Date: Tue, 6 Jul 2021 10:51:42 -0500
Subject: [wireless-regdb] [PATCH v2] wireless-regdb: recent FCC report
 and order allows 5850-5895 immediately
In-Reply-To: <10ffaa74a0779b7c7047de70cb1db7dfb0000022.1625068999.git.b.K.il.h.u+tigbuh@gmail.com>
References: <CAPuHQ=GbacSTgyimkJtx1FXp319Df=LdrPQZ6ZDnPQ_JVXueKw@mail.gmail.com>
 <10ffaa74a0779b7c7047de70cb1db7dfb0000022.1625068999.git.b.K.il.h.u+tigbuh@gmail.com>
Message-ID: <YOR8DtyIkVP0fg3f@ubuntu-x1>

On Wed, Jun 30, 2021 at 06:03:20PM +0200, bkil wrote:
> The new band is called U-NII-4.
> 
> The report recommends combining it with 5725-5895 to allow 160 MHz
> bandwidth, but that's technically not that easy with regdb due to the
> differing restrictions of the two parts. Marking the line for U-NII-3
> NO-OUTDOOR and PTMP-ONLY along with extending its range would be a
> possible workaround, but this needs to be discussed.
> 
> I don't see a requirement for TPC, hence reducing EIRP by 3dB is not
> needed. I've marked it 33dBm (minus 6dB for clients) to cope with 20MHz,
> but the band can support higher power, though the logic is complicated.
> 
> The upper subband (5895-5925 MHz) of the new band is reserved for ITS.
> 
> "We limit unlicensed use to indoor operations in recognition of the
> potential that ITS licensees may currently be operating"
> 
> "We also proposed that U-NII-4 devices be permitted to operate at the same
> power levels as U-NII-3 devices."
> 
> "For the U-NII-4 band, indoor access point EIRP will be limited to
> 33 dBm/20 MHz and 36 dBm/40 MHz. When combined with U-NII-3 band spectrum,
> indoor access point EIRP can scale to 36 dBm for 80 and 160 megahertz
> channels."
> 
> "Client devices would be limited to power levels 6 dB below the power
> limits for access points."
> 
> "the First Report and Order prohibit U-NII-4 client-to-client
> communications to protect co-channel incumbent ITS"
> 
> Signed-off-by: bkil <b.K.il.h.u+tigbuh at gmail.com>

Applied, thanks!


From seth.forshee at canonical.com  Tue Jul  6 09:17:39 2021
From: seth.forshee at canonical.com (Seth Forshee)
Date: Tue, 6 Jul 2021 11:17:39 -0500
Subject: [wireless-regdb] [PATCH] wireless-regdb: update 5725-5850 MHz
 rule for GB
In-Reply-To: <20210608141341.86462-1-seth.forshee@canonical.com>
References: <20210608141341.86462-1-seth.forshee@canonical.com>
Message-ID: <YOSCI2bhylSuW8GH@ubuntu-x1>

On Tue, Jun 08, 2021 at 09:13:41AM -0500, Seth Forshee wrote:
> Based on the latest IR 2030 update [1], update this range to cover
> 5725-5850 MHz rather than 5725-5875 MHz, increase the max EIRP to
> 200 mW, remove the DFS requirement, and add NO-OUTDOOR.
> 
> [1] https://www.ofcom.org.uk/__data/assets/pdf_file/0028/84970/ir-2030.pdf
> 
> Signed-off-by: Seth Forshee <seth.forshee at canonical.com>

Applied.


From seth.forshee at canonical.com  Tue Jul  6 09:32:02 2021
From: seth.forshee at canonical.com (Seth Forshee)
Date: Tue, 6 Jul 2021 11:32:02 -0500
Subject: [wireless-regdb] Different indoor and and outdoor constraints
 for the same band
In-Reply-To: <CAM1=_QQ-QG+mCLRxuY26S17zMb-gVEQNf0gWs13LxGYFk4mMYQ@mail.gmail.com>
References: <CAM1=_QQg6tpuctTwT2XVrz24aJ3Ei0SJzk-4tgd6dHvcrDtdPQ@mail.gmail.com>
 <YL9pQL+JV8CVDdaH@ubuntu-x1>
 <CAM1=_QQ-QG+mCLRxuY26S17zMb-gVEQNf0gWs13LxGYFk4mMYQ@mail.gmail.com>
Message-ID: <YOSFgurmZ/hHtteb@ubuntu-x1>

Sorry for the slow response. I've been on vacation.

On Wed, Jun 30, 2021 at 12:23:57AM +0200, Johan Almbladh wrote:
> On Tue, Jun 8, 2021 at 2:57 PM Seth Forshee <seth.forshee at canonical.com> wrote:
> >
> > On Wed, Jun 02, 2021 at 03:05:56PM +0200, Johan Almbladh wrote:
> > > The parser dbparse.py and nl80211.h understand the NO-INDOOR keyword,
> > > but I cannot find any occurrences of it in db.txt. Furthermore, as the
> > > reg domain rules are processed by cfg80211, the supported frequencies
> > > are annotated accordingly and NO-OUTDOOR is mapped to the flag
> > > NL80211_FREQUENCY_ATTR_INDOOR_ONLY. There is however no equivalent for
> > > the NO-INDOOR annotation.
> >
> > Correct, it is defined but completely unused. I suspect this is because
> > restrictions have been more common on outdoor use rather than indoor.
> 
> Yes, that makes sense.
> 
> > In principle we could have separate rules for indoor vs outdoor use, but
> > the regulatory support in the kernel can't currently deal with that. So
> > we would first need to add support in the kernel, but this would require
> > care to ensure older kernels can continue to use the regulatory
> > database.
> 
> I have been looking into this a bit. From what I can see in the
> regulatory support code in the Linux kernel, the outdoor environment
> mode could be handled by the same mechanism as indoor mode uses today.
> I can put together a patch set for review on the linux-wireless list.

There's a more fundamental problem to solve though. To my recollection
the kernel does not support duplicate rules for a given channel with
differing constraints.

> Backwards compatibility is more difficult. The problem I see is that
> the current kernel ignores the NO-INDOOR flag. If we add a band with
> this flag set in db.txt, older kernels will incorrectly use channels
> in that band. Solving this depends on where the compatibility is
> expected. I understand that db.txt must be portable and compatible
> with older kernels. From this file a binary database file is generated
> by the db2bin.py script. Does the binary database also need to be
> compatible with older kernels? If not, one solution could be to let
> db2bin.py take an an argument to include (or not) NO-INDOOR bands in
> the binary output. We could also bump the file version number so that
> older kernels won't accidentally use a binary database generated for a
> kernel with NO-INDOOR support. Otherwise, I see no other way than
> somehow putting the NO-INDOOR bands in a part of the binary file where
> older kernels cannot "see" it.

If they cannot handle duplicate rules for the same channel, there may be
some way to take advantage of the implementation to make sure they end
up using the rule we want them to use. I'm not sure without
refamiliarizing myself with the code.

> There is also the CRDA tool to consider for backwards compatibility.

CRDA only suports the older db format, and we can just limit that
database to having one of the rules for a given range, which we could
specify to be the rule without NO-INDOOR.

Seth


From johan.almbladh at anyfinetworks.com  Wed Jul  7 15:14:20 2021
From: johan.almbladh at anyfinetworks.com (Johan Almbladh)
Date: Thu, 8 Jul 2021 00:14:20 +0200
Subject: [wireless-regdb] Different indoor and and outdoor constraints
 for the same band
In-Reply-To: <YOSFgurmZ/hHtteb@ubuntu-x1>
References: <CAM1=_QQg6tpuctTwT2XVrz24aJ3Ei0SJzk-4tgd6dHvcrDtdPQ@mail.gmail.com>
 <YL9pQL+JV8CVDdaH@ubuntu-x1>
 <CAM1=_QQ-QG+mCLRxuY26S17zMb-gVEQNf0gWs13LxGYFk4mMYQ@mail.gmail.com>
 <YOSFgurmZ/hHtteb@ubuntu-x1>
Message-ID: <CAM1=_QSWxy-TxB-JsFFLDU7OoWJnv4qgV=hNfh3R-kxJ47uRcw@mail.gmail.com>

No worries! I've been busy with other stuff as well.

> > I have been looking into this a bit. From what I can see in the
> > regulatory support code in the Linux kernel, the outdoor environment
> > mode could be handled by the same mechanism as indoor mode uses today.
> > I can put together a patch set for review on the linux-wireless list.
>
> There's a more fundamental problem to solve though. To my recollection
> the kernel does not support duplicate rules for a given channel with
> differing constraints.

> If they cannot handle duplicate rules for the same channel, there may be
> some way to take advantage of the implementation to make sure they end
> up using the rule we want them to use. I'm not sure without
> refamiliarizing myself with the code.

Hmm, I understand. Thanks for the input. I will take a look and see
what we can do.

I have two concerns with the existing implementation in the Linux
kernel that I would like to address while doing this.

1) I think it would be best to not assume any specific structure among
the regulatory rules. The indoor bands and restrictions are not
necessarily a super set (or sub set) of the outdoor restrictions.
Regulated frequency bands should also be allowed to overlap,
completely or partially. Since regulatory bodies may (and do) specify
frequency bands like this in any order and with any restrictions, the
implementation should not make any assumptions about the rues.

2) If a rule in the data base has a flag that the kernel does not
understand, that rule should be ignored. In this particular case it
would have been fine if the kernel did not understand the NO-INDOOR
flag, but it should then have ignored the rule instead of using the
rule and just ignoring the flag.

Hopefully I will have some time next week to work on this.

> CRDA only suports the older db format, and we can just limit that
> database to having one of the rules for a given range, which we could
> specify to be the rule without NO-INDOOR.

Sounds good!

Johan


From seth.forshee at canonical.com  Thu Jul  8 12:42:12 2021
From: seth.forshee at canonical.com (Seth Forshee)
Date: Thu, 8 Jul 2021 14:42:12 -0500
Subject: [wireless-regdb] [PATCH v2] wireless-regdb: recent FCC report
 and order allows 5850-5895 immediately
In-Reply-To: <10ffaa74a0779b7c7047de70cb1db7dfb0000022.1625068999.git.b.K.il.h.u+tigbuh@gmail.com>
References: <CAPuHQ=GbacSTgyimkJtx1FXp319Df=LdrPQZ6ZDnPQ_JVXueKw@mail.gmail.com>
 <10ffaa74a0779b7c7047de70cb1db7dfb0000022.1625068999.git.b.K.il.h.u+tigbuh@gmail.com>
Message-ID: <YOdVFE51Wbxr80Qf@ubuntu-x1>

On Wed, Jun 30, 2021 at 06:03:20PM +0200, bkil wrote:
> The new band is called U-NII-4.
> 
> The report recommends combining it with 5725-5895 to allow 160 MHz
> bandwidth, but that's technically not that easy with regdb due to the
> differing restrictions of the two parts. Marking the line for U-NII-3
> NO-OUTDOOR and PTMP-ONLY along with extending its range would be a
> possible workaround, but this needs to be discussed.
> 
> I don't see a requirement for TPC, hence reducing EIRP by 3dB is not
> needed. I've marked it 33dBm (minus 6dB for clients) to cope with 20MHz,
> but the band can support higher power, though the logic is complicated.
> 
> The upper subband (5895-5925 MHz) of the new band is reserved for ITS.
> 
> "We limit unlicensed use to indoor operations in recognition of the
> potential that ITS licensees may currently be operating"
> 
> "We also proposed that U-NII-4 devices be permitted to operate at the same
> power levels as U-NII-3 devices."
> 
> "For the U-NII-4 band, indoor access point EIRP will be limited to
> 33 dBm/20 MHz and 36 dBm/40 MHz. When combined with U-NII-3 band spectrum,
> indoor access point EIRP can scale to 36 dBm for 80 and 160 megahertz
> channels."
> 
> "Client devices would be limited to power levels 6 dB below the power
> limits for access points."
> 
> "the First Report and Order prohibit U-NII-4 client-to-client
> communications to protect co-channel incumbent ITS"
> 
> Signed-off-by: bkil <b.K.il.h.u+tigbuh at gmail.com>
> ---
>  db.txt | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/db.txt b/db.txt
> index c71a03a..ae6ea31 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -1587,7 +1587,10 @@ country US: DFS-FCC
>  	# requirements, we can extend the range by 5 MHz to make the kernel
>  	# happy and be able to use channel 144.
>  	(5470 - 5730 @ 160), (23), DFS
> -	(5730 - 5850 @ 80), (30)
> +	(5730 - 5850 @ 160), (30), AUTO-BW
> +	# https://www.federalregister.gov/documents/2021/05/03/2021-08802/use-of-the-5850-5925-ghz-band
> +	# max. 33 dBm AP @ 20MHz, 36 dBm AP @ 40Mhz+, 6 dB less for clients
> +	(5850 - 5895 @ 160), (27), NO-OUTDOOR, PTMP-ONLY, AUTO-BW, NO-IR

I discovered a couple of problems here.

The first is that it seems I forgot to test build this patch before I
pushed it. The PTMP-ONLY flag isn't allowed by db2fw.py. This was done
by Johannes for reasons which aren't explained, so maybe he can shed
some light on it. The flag doesn't appear to be used by the kernel or
hostapd, so maybe it was deprecated long ago. Anyway, I've pushed a
change to remove this flag.

The second problem is more serious. I thought that we could allow 160
MHz bandwidth across two AUTO-BW ranges too small for this bandwidth,
but it turns out that the kernel rejects any rules with a bandwidth
greater than the frequency range of the rule. I'm not sure what we can
do about this. Even if the kernel were changed to support allowing
greater bandwidths across combined ranges, we're going to have a
backwards compatibility problem with older kernels.

Seth


From seth.forshee at canonical.com  Wed Jul 14 09:44:12 2021
From: seth.forshee at canonical.com (Seth Forshee)
Date: Wed, 14 Jul 2021 11:44:12 -0500
Subject: [wireless-regdb] [ANN] wireless-regdb: master-2021-07-14
Message-ID: <YO8UXAyCvWqUo7xf@ubuntu-x1>

A new release of wireless-regdb (master-2021-07-14) is available at:

https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2021.07.14.tar.xz

The short log of changes since the master-2021-04-21 release is below.

Thanks,
Seth

---

Seth Forshee (4):
      wireless-regdb: update 5725-5850 MHz rule for GB
      wireless-regdb: remove PTMP-ONLY from 5850-5895 MHz for US
      wireless-regdb: reduce bandwidth for 5730-5850 and 5850-5895 MHz in US
      wireless-regdb: update regulatory database based on preceding changes

bkil (1):
      wireless-regdb: recent FCC report and order allows 5850-5895 immediately


From timo.witte at gmail.com  Sun Jul 18 17:20:34 2021
From: timo.witte at gmail.com (Timo Witte)
Date: Mon, 19 Jul 2021 02:20:34 +0200
Subject: [wireless-regdb] wireless-regdb: Update regulatory rules for
 Germany (DE) on 6GHz
In-Reply-To: <CANB4YXTf0DhJfL6kPa26ZCzj8FRwwdw_enGROzL-zXuWGyrwOQ@mail.gmail.com>
References: <CANB4YXTf0DhJfL6kPa26ZCzj8FRwwdw_enGROzL-zXuWGyrwOQ@mail.gmail.com>
Message-ID: <CANB4YXRtyvgu946rL=gxaRqhXja1qfBQ+DSYfiMvYcax7o45EQ@mail.gmail.com>

The bundesnetzagentur has assigned WiFi 6E frequencies for germany you
this is the
publication of that change:
https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/MobilfunkDectWlanCBFunk/vfg552021WLAN6GHz.pdf?__blob=publicationFile&v=3

Following frequencies have been assigned for general use:
5945 - 6425 Mhz
maximum (200 mW)
No outdoor usage is allowed for 200mW

For "very low power devices" outdoor usage
is allowed, but only with (25 mW)
same frequency range 5945 - 6425

There is no DFS requirement.

Best regards,
Timo


From sforshee at kernel.org  Wed Jul 21 07:29:06 2021
From: sforshee at kernel.org (Seth Forshee)
Date: Wed, 21 Jul 2021 09:29:06 -0500
Subject: [wireless-regdb] wireless-regdb: Update regulatory rules for
 Germany (DE) on 6GHz
In-Reply-To: <CANB4YXRtyvgu946rL=gxaRqhXja1qfBQ+DSYfiMvYcax7o45EQ@mail.gmail.com>
References: <CANB4YXTf0DhJfL6kPa26ZCzj8FRwwdw_enGROzL-zXuWGyrwOQ@mail.gmail.com>
 <CANB4YXRtyvgu946rL=gxaRqhXja1qfBQ+DSYfiMvYcax7o45EQ@mail.gmail.com>
Message-ID: <YPgvMph+3vRbrol3@ubuntu-x1>

On Mon, Jul 19, 2021 at 02:20:34AM +0200, Timo Witte wrote:
> The bundesnetzagentur has assigned WiFi 6E frequencies for germany you
> this is the
> publication of that change:
> https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/MobilfunkDectWlanCBFunk/vfg552021WLAN6GHz.pdf?__blob=publicationFile&v=3
> 
> Following frequencies have been assigned for general use:
> 5945 - 6425 Mhz
> maximum (200 mW)
> No outdoor usage is allowed for 200mW
> 
> For "very low power devices" outdoor usage
> is allowed, but only with (25 mW)
> same frequency range 5945 - 6425
> 
> There is no DFS requirement.

This all matches with my reading of a translated version of the
document. Do you plan to send a patch to add this range? If not, I can
send one.

Thanks,
Seth


From sforshee at kernel.org  Wed Jul 21 08:27:24 2021
From: sforshee at kernel.org (Seth Forshee)
Date: Wed, 21 Jul 2021 10:27:24 -0500
Subject: [wireless-regdb] wireless-regdb: Update regulatory rules for
 Germany (DE) on 6GHz
In-Reply-To: <CANB4YXSDuYndC26KPkV+XqPkowbN54MMceuj7MNaxh+EwLN4kw@mail.gmail.com>
References: <CANB4YXTf0DhJfL6kPa26ZCzj8FRwwdw_enGROzL-zXuWGyrwOQ@mail.gmail.com>
 <CANB4YXRtyvgu946rL=gxaRqhXja1qfBQ+DSYfiMvYcax7o45EQ@mail.gmail.com>
 <YPgvMph+3vRbrol3@ubuntu-x1>
 <CANB4YXSDuYndC26KPkV+XqPkowbN54MMceuj7MNaxh+EwLN4kw@mail.gmail.com>
Message-ID: <YPg83HXFIXDAEFx1@ubuntu-x1>

On Wed, Jul 21, 2021 at 04:57:03PM +0200, Timo Witte wrote:
> From f9a99269b00f961e40024632c7b831c615bfa392 Mon Sep 17 00:00:00 2001
> From: Timo Witte <timo.witte at gmail.com>
> Date: Wed, 21 Jul 2021 16:51:40 +0200
> Subject: [PATCH] add wifi6e for germany
> 
> Signed-off-by: Timo Witte <timo.witte at gmail.com>
> ---
>  db.txt | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/db.txt b/db.txt
> index 1e5ed03..411b7ac 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -448,6 +448,12 @@ country CZ: DFS-ETSI
>  # Bereich 57 GHz - 66 GHz f?r Funkanwendungen f?r weitbandige
>  # Daten?bertragungssysteme; ?Multiple Gigabit WAS/RLAN Systems (MGWS)?).
>  # https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/2011_08_MGWS_pdf.pdf
> +#
> +# Allocation for the WiFi 6E Band (Allgemeinzuteilung von Frequenzen im
> +# Bereich 5945 MHz - 6425 MHz f?r drahtlose Zugangssysteme,
> +# einschlie?lich lokaler Funknetze WAS/WLAN (?Wireless Access Systems
> +# including Wireless Local Area Networks?))
> +# https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/MobilfunkDectWlanCBFunk/vfg552021WLAN6GHz.pdf
>  country DE: DFS-ETSI
>         (2400 - 2483.5 @ 40), (100 mW)
>         (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
> @@ -455,6 +461,10 @@ country DE: DFS-ETSI
>         (5470 - 5725 @ 160), (500 mW), DFS, wmmrule=ETSI
>         # short range devices (ETSI EN 300 440-1)
>         (5725 - 5875 @ 80), (25 mW)
> +       # WiFi 6E
> +       (5945 - 6425 @ 160), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
> +       # WiFi 6E Short range (Outdoor allowed)
> +       (5945 - 6425 @ 160), (25 mW), AUTO-BW, wmmrule=ETSI

Unfortunately the kernel doesn't support multiple rules for a given
range with differing flags. Currently it is necessary to specify either
the indoor power limit with NO-OUTDOOR or the outdoor power limit, but
not both.

Thanks,
Seth


From timo.witte at gmail.com  Wed Jul 21 07:55:17 2021
From: timo.witte at gmail.com (Timo Witte)
Date: Wed, 21 Jul 2021 16:55:17 +0200
Subject: [wireless-regdb] wireless-regdb: Update regulatory rules for
 Germany (DE) on 6GHz
In-Reply-To: <YPgvMph+3vRbrol3@ubuntu-x1>
References: <CANB4YXTf0DhJfL6kPa26ZCzj8FRwwdw_enGROzL-zXuWGyrwOQ@mail.gmail.com>
 <CANB4YXRtyvgu946rL=gxaRqhXja1qfBQ+DSYfiMvYcax7o45EQ@mail.gmail.com>
 <YPgvMph+3vRbrol3@ubuntu-x1>
Message-ID: <CANB4YXRcr=XM00r_mz2ejAfuYwHMibffOcxNiDP=acpmFUchMA@mail.gmail.com>

Signed-off-by: Timo Witte <timo.witte at gmail.com>
---
 db.txt | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/db.txt b/db.txt
index 1e5ed03..411b7ac 100644
--- a/db.txt
+++ b/db.txt
@@ -448,6 +448,12 @@ country CZ: DFS-ETSI
 # Bereich 57 GHz - 66 GHz f?r Funkanwendungen f?r weitbandige
 # Daten?bertragungssysteme; ?Multiple Gigabit WAS/RLAN Systems (MGWS)?).
 # https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/2011_08_MGWS_pdf.pdf
+#
+# Allocation for the WiFi 6E Band (Allgemeinzuteilung von Frequenzen im
+# Bereich 5945 MHz - 6425 MHz f?r drahtlose Zugangssysteme,
+# einschlie?lich lokaler Funknetze WAS/WLAN (?Wireless Access Systems
+# including Wireless Local Area Networks?))
+# https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/MobilfunkDectWlanCBFunk/v>
 country DE: DFS-ETSI
        (2400 - 2483.5 @ 40), (100 mW)
        (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
@@ -455,6 +461,10 @@ country DE: DFS-ETSI
        (5470 - 5725 @ 160), (500 mW), DFS, wmmrule=ETSI
        # short range devices (ETSI EN 300 440-1)
        (5725 - 5875 @ 80), (25 mW)
+       # WiFi 6E
+       (5945 - 6425 @ 160), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
+       # WiFi 6E Short range (Outdoor allowed)
+       (5945 - 6425 @ 160), (25 mW), AUTO-BW, wmmrule=ETSI
        # 60 GHz band channels 1-4 (ETSI EN 302 567)
        (57000 - 66000 @ 2160), (40)

-- 
2.31.1

On Wed, Jul 21, 2021 at 4:29 PM Seth Forshee <sforshee at kernel.org> wrote:
>
> On Mon, Jul 19, 2021 at 02:20:34AM +0200, Timo Witte wrote:
> > The bundesnetzagentur has assigned WiFi 6E frequencies for germany you
> > this is the
> > publication of that change:
> > https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/MobilfunkDectWlanCBFunk/vfg552021WLAN6GHz.pdf?__blob=publicationFile&v=3
> >
> > Following frequencies have been assigned for general use:
> > 5945 - 6425 Mhz
> > maximum (200 mW)
> > No outdoor usage is allowed for 200mW
> >
> > For "very low power devices" outdoor usage
> > is allowed, but only with (25 mW)
> > same frequency range 5945 - 6425
> >
> > There is no DFS requirement.
>
> This all matches with my reading of a translated version of the
> document. Do you plan to send a patch to add this range? If not, I can
> send one.
>
> Thanks,
> Seth


From timo.witte at gmail.com  Wed Jul 21 07:57:03 2021
From: timo.witte at gmail.com (Timo Witte)
Date: Wed, 21 Jul 2021 16:57:03 +0200
Subject: [wireless-regdb] wireless-regdb: Update regulatory rules for
 Germany (DE) on 6GHz
In-Reply-To: <YPgvMph+3vRbrol3@ubuntu-x1>
References: <CANB4YXTf0DhJfL6kPa26ZCzj8FRwwdw_enGROzL-zXuWGyrwOQ@mail.gmail.com>
 <CANB4YXRtyvgu946rL=gxaRqhXja1qfBQ+DSYfiMvYcax7o45EQ@mail.gmail.com>
 <YPgvMph+3vRbrol3@ubuntu-x1>
Message-ID: <CANB4YXSDuYndC26KPkV+XqPkowbN54MMceuj7MNaxh+EwLN4kw@mail.gmail.com>

>From f9a99269b00f961e40024632c7b831c615bfa392 Mon Sep 17 00:00:00 2001
From: Timo Witte <timo.witte at gmail.com>
Date: Wed, 21 Jul 2021 16:51:40 +0200
Subject: [PATCH] add wifi6e for germany

Signed-off-by: Timo Witte <timo.witte at gmail.com>
---
 db.txt | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/db.txt b/db.txt
index 1e5ed03..411b7ac 100644
--- a/db.txt
+++ b/db.txt
@@ -448,6 +448,12 @@ country CZ: DFS-ETSI
 # Bereich 57 GHz - 66 GHz f?r Funkanwendungen f?r weitbandige
 # Daten?bertragungssysteme; ?Multiple Gigabit WAS/RLAN Systems (MGWS)?).
 # https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/2011_08_MGWS_pdf.pdf
+#
+# Allocation for the WiFi 6E Band (Allgemeinzuteilung von Frequenzen im
+# Bereich 5945 MHz - 6425 MHz f?r drahtlose Zugangssysteme,
+# einschlie?lich lokaler Funknetze WAS/WLAN (?Wireless Access Systems
+# including Wireless Local Area Networks?))
+# https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/MobilfunkDectWlanCBFunk/vfg552021WLAN6GHz.pdf
 country DE: DFS-ETSI
        (2400 - 2483.5 @ 40), (100 mW)
        (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
@@ -455,6 +461,10 @@ country DE: DFS-ETSI
        (5470 - 5725 @ 160), (500 mW), DFS, wmmrule=ETSI
        # short range devices (ETSI EN 300 440-1)
        (5725 - 5875 @ 80), (25 mW)
+       # WiFi 6E
+       (5945 - 6425 @ 160), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
+       # WiFi 6E Short range (Outdoor allowed)
+       (5945 - 6425 @ 160), (25 mW), AUTO-BW, wmmrule=ETSI
        # 60 GHz band channels 1-4 (ETSI EN 302 567)
        (57000 - 66000 @ 2160), (40)

-- 
2.31.1

On Wed, Jul 21, 2021 at 4:29 PM Seth Forshee <sforshee at kernel.org> wrote:
>
> On Mon, Jul 19, 2021 at 02:20:34AM +0200, Timo Witte wrote:
> > The bundesnetzagentur has assigned WiFi 6E frequencies for germany you
> > this is the
> > publication of that change:
> > https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/MobilfunkDectWlanCBFunk/vfg552021WLAN6GHz.pdf?__blob=publicationFile&v=3
> >
> > Following frequencies have been assigned for general use:
> > 5945 - 6425 Mhz
> > maximum (200 mW)
> > No outdoor usage is allowed for 200mW
> >
> > For "very low power devices" outdoor usage
> > is allowed, but only with (25 mW)
> > same frequency range 5945 - 6425
> >
> > There is no DFS requirement.
>
> This all matches with my reading of a translated version of the
> document. Do you plan to send a patch to add this range? If not, I can
> send one.
>
> Thanks,
> Seth


From timo.witte at gmail.com  Wed Jul 21 08:51:53 2021
From: timo.witte at gmail.com (Timo Witte)
Date: Wed, 21 Jul 2021 17:51:53 +0200
Subject: [wireless-regdb] wireless-regdb: Update regulatory rules for
 Germany (DE) on 6GHz
In-Reply-To: <YPg83HXFIXDAEFx1@ubuntu-x1>
References: <CANB4YXTf0DhJfL6kPa26ZCzj8FRwwdw_enGROzL-zXuWGyrwOQ@mail.gmail.com>
 <CANB4YXRtyvgu946rL=gxaRqhXja1qfBQ+DSYfiMvYcax7o45EQ@mail.gmail.com>
 <YPgvMph+3vRbrol3@ubuntu-x1>
 <CANB4YXSDuYndC26KPkV+XqPkowbN54MMceuj7MNaxh+EwLN4kw@mail.gmail.com>
 <YPg83HXFIXDAEFx1@ubuntu-x1>
Message-ID: <CANB4YXS64QtxsgY0bx_Ri7bWfTY_5Ry7PbGwaGT3QVZb380vgQ@mail.gmail.com>

Ok then let's just remove the 25mW line.
Here is the new patch:

diff --git a/db.txt b/db.txt
index 1e5ed03..debd878 100644
--- a/db.txt
+++ b/db.txt
@@ -448,6 +448,12 @@ country CZ: DFS-ETSI
 # Bereich 57 GHz - 66 GHz f?r Funkanwendungen f?r weitbandige
 # Daten?bertragungssysteme; ?Multiple Gigabit WAS/RLAN Systems (MGWS)?).
 # https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/2011_08_MGWS_pdf.pdf
+#
+# Allocation for the WiFi 6E Band (Allgemeinzuteilung von Frequenzen im
+# Bereich 5945 MHz - 6425 MHz f?r drahtlose Zugangssysteme,
+# einschlie?lich lokaler Funknetze WAS/WLAN (?Wireless Access Systems
+# including Wireless Local Area Networks?))
+# https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/MobilfunkDectWlanCBFunk/vfg552021WLAN6GHz.pdf
 country DE: DFS-ETSI
  (2400 - 2483.5 @ 40), (100 mW)
  (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
@@ -455,6 +461,8 @@ country DE: DFS-ETSI
  (5470 - 5725 @ 160), (500 mW), DFS, wmmrule=ETSI
  # short range devices (ETSI EN 300 440-1)
  (5725 - 5875 @ 80), (25 mW)
+ # WiFi 6E
+ (5945 - 6425 @ 160), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
  # 60 GHz band channels 1-4 (ETSI EN 302 567)
  (57000 - 66000 @ 2160), (40)


On Wed, Jul 21, 2021 at 5:27 PM Seth Forshee <sforshee at kernel.org> wrote:
>
> On Wed, Jul 21, 2021 at 04:57:03PM +0200, Timo Witte wrote:
> > From f9a99269b00f961e40024632c7b831c615bfa392 Mon Sep 17 00:00:00 2001
> > From: Timo Witte <timo.witte at gmail.com>
> > Date: Wed, 21 Jul 2021 16:51:40 +0200
> > Subject: [PATCH] add wifi6e for germany
> >
> > Signed-off-by: Timo Witte <timo.witte at gmail.com>
> > ---
> >  db.txt | 10 ++++++++++
> >  1 file changed, 10 insertions(+)
> >
> > diff --git a/db.txt b/db.txt
> > index 1e5ed03..411b7ac 100644
> > --- a/db.txt
> > +++ b/db.txt
> > @@ -448,6 +448,12 @@ country CZ: DFS-ETSI
> >  # Bereich 57 GHz - 66 GHz f?r Funkanwendungen f?r weitbandige
> >  # Daten?bertragungssysteme; ?Multiple Gigabit WAS/RLAN Systems (MGWS)?).
> >  # https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/2011_08_MGWS_pdf.pdf
> > +#
> > +# Allocation for the WiFi 6E Band (Allgemeinzuteilung von Frequenzen im
> > +# Bereich 5945 MHz - 6425 MHz f?r drahtlose Zugangssysteme,
> > +# einschlie?lich lokaler Funknetze WAS/WLAN (?Wireless Access Systems
> > +# including Wireless Local Area Networks?))
> > +# https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/MobilfunkDectWlanCBFunk/vfg552021WLAN6GHz.pdf
> >  country DE: DFS-ETSI
> >         (2400 - 2483.5 @ 40), (100 mW)
> >         (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
> > @@ -455,6 +461,10 @@ country DE: DFS-ETSI
> >         (5470 - 5725 @ 160), (500 mW), DFS, wmmrule=ETSI
> >         # short range devices (ETSI EN 300 440-1)
> >         (5725 - 5875 @ 80), (25 mW)
> > +       # WiFi 6E
> > +       (5945 - 6425 @ 160), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
> > +       # WiFi 6E Short range (Outdoor allowed)
> > +       (5945 - 6425 @ 160), (25 mW), AUTO-BW, wmmrule=ETSI
>
> Unfortunately the kernel doesn't support multiple rules for a given
> range with differing flags. Currently it is necessary to specify either
> the indoor power limit with NO-OUTDOOR or the outdoor power limit, but
> not both.
>
> Thanks,
> Seth


From timo.witte at gmail.com  Sat Jul 31 18:42:42 2021
From: timo.witte at gmail.com (Timo Witte)
Date: Sun, 1 Aug 2021 03:42:42 +0200
Subject: [wireless-regdb] wireless-regdb: Update regulatory rules for
 Germany (DE) on 6GHz
In-Reply-To: <CANB4YXS64QtxsgY0bx_Ri7bWfTY_5Ry7PbGwaGT3QVZb380vgQ@mail.gmail.com>
References: <CANB4YXTf0DhJfL6kPa26ZCzj8FRwwdw_enGROzL-zXuWGyrwOQ@mail.gmail.com>
 <CANB4YXRtyvgu946rL=gxaRqhXja1qfBQ+DSYfiMvYcax7o45EQ@mail.gmail.com>
 <YPgvMph+3vRbrol3@ubuntu-x1>
 <CANB4YXSDuYndC26KPkV+XqPkowbN54MMceuj7MNaxh+EwLN4kw@mail.gmail.com>
 <YPg83HXFIXDAEFx1@ubuntu-x1>
 <CANB4YXS64QtxsgY0bx_Ri7bWfTY_5Ry7PbGwaGT3QVZb380vgQ@mail.gmail.com>
Message-ID: <CANB4YXTKpu3gOJ4om8yo6ZSvnS497tk1cU-=56TGaktY2QBV-g@mail.gmail.com>

Any updates on this Seth?
can we just add the "NO-OUTDOOR" line then as i did in my updated
patch, if the kernel does not support overlapping / identical
frequency ranges with different power limits?

Best regards,
Timo


On Wed, Jul 21, 2021 at 5:51 PM Timo Witte <timo.witte at gmail.com> wrote:
>
> Ok then let's just remove the 25mW line.
> Here is the new patch:
>
> diff --git a/db.txt b/db.txt
> index 1e5ed03..debd878 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -448,6 +448,12 @@ country CZ: DFS-ETSI
>  # Bereich 57 GHz - 66 GHz f?r Funkanwendungen f?r weitbandige
>  # Daten?bertragungssysteme; ?Multiple Gigabit WAS/RLAN Systems (MGWS)?).
>  # https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/2011_08_MGWS_pdf.pdf
> +#
> +# Allocation for the WiFi 6E Band (Allgemeinzuteilung von Frequenzen im
> +# Bereich 5945 MHz - 6425 MHz f?r drahtlose Zugangssysteme,
> +# einschlie?lich lokaler Funknetze WAS/WLAN (?Wireless Access Systems
> +# including Wireless Local Area Networks?))
> +# https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/MobilfunkDectWlanCBFunk/vfg552021WLAN6GHz.pdf
>  country DE: DFS-ETSI
>   (2400 - 2483.5 @ 40), (100 mW)
>   (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
> @@ -455,6 +461,8 @@ country DE: DFS-ETSI
>   (5470 - 5725 @ 160), (500 mW), DFS, wmmrule=ETSI
>   # short range devices (ETSI EN 300 440-1)
>   (5725 - 5875 @ 80), (25 mW)
> + # WiFi 6E
> + (5945 - 6425 @ 160), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
>   # 60 GHz band channels 1-4 (ETSI EN 302 567)
>   (57000 - 66000 @ 2160), (40)
>
>
> On Wed, Jul 21, 2021 at 5:27 PM Seth Forshee <sforshee at kernel.org> wrote:
> >
> > On Wed, Jul 21, 2021 at 04:57:03PM +0200, Timo Witte wrote:
> > > From f9a99269b00f961e40024632c7b831c615bfa392 Mon Sep 17 00:00:00 2001
> > > From: Timo Witte <timo.witte at gmail.com>
> > > Date: Wed, 21 Jul 2021 16:51:40 +0200
> > > Subject: [PATCH] add wifi6e for germany
> > >
> > > Signed-off-by: Timo Witte <timo.witte at gmail.com>
> > > ---
> > >  db.txt | 10 ++++++++++
> > >  1 file changed, 10 insertions(+)
> > >
> > > diff --git a/db.txt b/db.txt
> > > index 1e5ed03..411b7ac 100644
> > > --- a/db.txt
> > > +++ b/db.txt
> > > @@ -448,6 +448,12 @@ country CZ: DFS-ETSI
> > >  # Bereich 57 GHz - 66 GHz f?r Funkanwendungen f?r weitbandige
> > >  # Daten?bertragungssysteme; ?Multiple Gigabit WAS/RLAN Systems (MGWS)?).
> > >  # https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/2011_08_MGWS_pdf.pdf
> > > +#
> > > +# Allocation for the WiFi 6E Band (Allgemeinzuteilung von Frequenzen im
> > > +# Bereich 5945 MHz - 6425 MHz f?r drahtlose Zugangssysteme,
> > > +# einschlie?lich lokaler Funknetze WAS/WLAN (?Wireless Access Systems
> > > +# including Wireless Local Area Networks?))
> > > +# https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/MobilfunkDectWlanCBFunk/vfg552021WLAN6GHz.pdf
> > >  country DE: DFS-ETSI
> > >         (2400 - 2483.5 @ 40), (100 mW)
> > >         (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
> > > @@ -455,6 +461,10 @@ country DE: DFS-ETSI
> > >         (5470 - 5725 @ 160), (500 mW), DFS, wmmrule=ETSI
> > >         # short range devices (ETSI EN 300 440-1)
> > >         (5725 - 5875 @ 80), (25 mW)
> > > +       # WiFi 6E
> > > +       (5945 - 6425 @ 160), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
> > > +       # WiFi 6E Short range (Outdoor allowed)
> > > +       (5945 - 6425 @ 160), (25 mW), AUTO-BW, wmmrule=ETSI
> >
> > Unfortunately the kernel doesn't support multiple rules for a given
> > range with differing flags. Currently it is necessary to specify either
> > the indoor power limit with NO-OUTDOOR or the outdoor power limit, but
> > not both.
> >
> > Thanks,
> > Seth


