Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
Update the frequency ranges and power limits according to the current Ecuadorian norm [1], allow up to 160 MHz bandwidth on 5GHz. [1] https://www.arcotel.gob.ec/wp-content/uploads/2018/04/NORMA-ESPECTRO-DE-USO-LIBRE-Y-ESPECTRO-PARA-USO-DETERMINADO-EN-BANDAS-LIBRES.pdf Signed-off-by: Victor Bayas <victorsbayas@gmail.com> Signed-off-by: Seth Forshee <sforshee@kernel.org>
The Norwegian regulatory authority (NKOM) has updated the existing regulations. WiFi 6E is now allowed with the same restrictions as in many/most EU/EEA countries - i.e 200 mW indoor and 25 mW outdoor, Using the DE entry as a template for now, until this dual entry can be described in the database. The update also extended the 60 GHz band to 71 GHz. The official announcement of the regulation changes: https://lovdata.no/dokument/LTI/forskrift/2021-06-29-2312 The existing reference in the database has been updated with these changes, so no new reference is needed. Signed-off-by: Bjørn Mork <bjorn@mork.no> Signed-off-by: Seth Forshee <sforshee@kernel.org>
Signed-off-by: Timo Witte <timo.witte@gmail.com> Signed-off-by: Seth Forshee <sforshee@kernel.org>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
The kernel doesn't allow rules with bandwidth greater than the rule channel width, even when adjacent rules with AUTO_BW an accomodate the bandwidth. Reduce the bandwidths for now to create rules which the kernel will accept. Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
Added in commit 9839e1e389b5 ("wireless-regdb: recent FCC report and
order allows 5850-5895 immediately"), this flag is unused by the
kernel and hostapd. The flag is also restricted from being present
by db2fw.py, so remove it.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
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@gmail.com> Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
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@canonical.com>