| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
As announced [1], I am taking over maintainership of the wireless
regulatory database.
Make it official by replacing the key and certificate, and updating
maintainership information in various places.
[1] https://lore.kernel.org/all/CAGb2v657baNMPKU3QADijx7hZa=GUcSv2LEDdn6N=QQaFX8r-g@mail.gmail.com/
Signed-off-by: Chen-Yu Tsai <wens@kernel.org>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
- Update legislation link from March 2022 version to June 2023.
- Add comments for each frequency range referring back to legislation.
- Switch units from dBm to mW to match values listed in legislation.
- Allow 5850-5875 at low power, as this has always been permitted.
- Combine 5150-5350 bands to permit a 160 MHz channel.
Signed-off-by: Adam Nielsen <a.nielsen@shikadi.net>
[ saf:
- eliminate overlapping rules
- add AUTO-BW for 5730-5850 MHz and 5850-5875 MHz
- change max bw for 5850-5875 MHz to 20 MHz ]
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Based on [1], add support for 6GHz and make minor adjustments to other
ranges.
[1] https://www.btk.gov.tr/uploads/pages/ftm-teknik-olcutler-ek-5.pdf
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
guidelines
The radio spectrum guidelines document from March 2022 [1] contains no
restriction on outdoor operation and allows use of 57-66 GHz.
[1] https://www.tra.gov.eg/wp-content/uploads/2022/03/EGY-NTRA-March-2022-SRD_English_Final.pdf
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Update frequency ranges and max EIRP for 2.4 GHz and 5 GHz, and add
support for 57-66 GHz based on NTC PH memorandum circulars.
Signed-off-by: kleo <kleo@hak.dog>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Update frequency ranges and max EIRP for 2.4 GHz and 5 GHz, and add support for
6 GHz based on latest HK regulations.
Source:
https://www.ofca.gov.hk/filemanager/ofca/en/content_401/hkca1039.pdf (2.4 GHz and 5 GHz)
https://www.ofca.gov.hk/filemanager/ofca/en/content_401/hkca1081.pdf (6 GHz)
Signed-off-by: Tavio Wong <tavio.wong@proton.me>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Increase the max EIRP for 2.4 GHz to 30 dBm, and add DFS for 5250-5350
MHz and 5470-5725 MHz.
Source:
https://dot.gov.in/spectrummanagement/delicensing-24-24835-ghz-band-gsr-45-e-5150-5350-ghz-gsr-46-e-and-5725-5875-ghz
https://dot.gov.in/spectrummanagement/license-exemption-5-ghz-gsr-1048e-dated-22102018
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Use of Wi-Fi devices are regulated by the Decision of the State Commission for Radio Frequencies
under the Ministry of Communications of Russia of February 29, 2016 No. 16-36-03
“On Amendments to the Decision of the State Committee for Radio Frequencies of May 7, 2007 No. 07-20-03-001
“On the allocation of radio frequency bands to short-range devices »
https://www.garant.ru/products/ipo/prime/doc/71249926/
The document sets 100mW for 2.4 GHz and 200 mW for 5 GHz.
There is a special limitation 100mW for 5 GHz onboard aircraft.
DFS was never required in Russia.
Instead the authority chose to prohibit outdoor use for 5 GHz totally.
There is a vague comment that power should be automatically reduced in direction of other devices.
This can be interpreted as a TPC requirement, but in practice devices are certified with 200mW.
Signed-off-by: Dmitry Tunin <hanipouspilot@gmail.com>
[ saf: keep 5 GHz power limits at 100 mW due to TPC requirement ]
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Update regulatory info for Russia on 6GHz in
accordance with current regulatory rules.
Source: https://docs.cntd.ru/document/1300597464?section=text
Signed-off-by: Kirill Matvienko <me@16depo.xyz>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Update regulatory info for Russia on 5GHz in accordance with
current regulatory rules.
Source: https://docs.cntd.ru/document/902048009?section=text
Signed-off-by: Eugene Konev <uejikov@gmail.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Support 6GHz for JP Region.
The Ministry of Internal Affairs and Communications has approved 6GHz (5925 - 6425 MHz) in Japan.
Source: https://www.soumu.go.jp/main_content/000833682.pdf
Signed-off-by: CaffeeLake <PascalCoffeeLake@gmail.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Support 144ch for JP Region.
The Ministry of Internal Affairs and Communications has approved 144ch in Japan.
Source: https://www.soumu.go.jp/main_content/000635492.pdf
Signed-off-by: CaffeeLake <PascalCoffeeLake@gmail.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Switzerland has since approved the use of the 6 GHz spectrum as well as
allowed the unlicensed use of the 66-71 GHz spectrum.
See https://www.ofcomnet.ch/api/rir/1010 for the current regulatory
overview in Switzerland.
Signed-off-by: Lorenz Brun <lorenz@brun.one>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
The rules for Brazil in wireless-regdb have no comment indicating where
they came from, and haven't been updated in a long time. There have been
some changes to the legislation since then, including the addition of
the 6 GHz and 60 GHz ranges.
Signed-off-by: Cesar Eduardo Barros <cesarb@cesarb.eti.br>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
[1] contains updated information for 5 GHz in PK as well as information
for 60 GHz use. Update the rules to match.
[1] https://www.pta.gov.pk/assets/media/iot_srd_regulatory_framework_01-06-2022.pdf
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Add 5 GHz rules which were provided by a representative of the Guyana
Telecommunications Agency. There is no published document which can be
used as a reference for these rules.
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Article 3 of Decision (EU) 2021/1067 states that member states must
adopt rules for harmonised use of the 5945-6425 MHz band by Dec 1, 2021.
Update rules for all member states to include a reference to the
decision, and add the rule for countries which do not yet have it.
Some countries currently have the power limit specified as 200 mW.
Update these countries to use the 23 dBm limit specified by the decision
instead, which is equivalent.
Suggested-by: Dennis Bland <dennis@dbperformance.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
No other bands are directly adjacent to this one, so AUTO-BW doesn't
make sense. Remove it, and also fix a nearby whitespace mistake found
while doing this update.
Cc: Dennis Bland <dennis@dbperformance.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Reviewed-by: Petko Bordjukov <bordjukov@gmail.com>
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Add 6 GHz operation for FI:
https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32021D1067&from=EN
Signed-off-by: Dennis Bland <dennis@dbperformance.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
With the 6 GHz band (U-NII-5, U-NII-6, U-NII-7, U-NII-8) in USA, the FCC
introduces the concept of a fixed PSD (Power Spectral Density) for all
supported 6 GHz channel widths for LPI (Low Power Indoor) environments.
Wider channel widths have a higher noise floor, therefore specifying a
fixed PSD allows wider channels to operate at a higher EIRP to maintain
the same S/N ratio as smaller channel widths.
While the 6 GHz specification also allows a "Standard" power mode with
higher EIRP and PSD limits, these devices are also required to employ
AFC (Automatic Frequency Coordination) which normally requires GNSS.
Currently there is no way to specify different EIRP and PSD levels for
APC and non-APC devices. Therefore, only LPI mode is considered here.
LPI requires non-client (AP) devices to have a maximum PSD of 5 dBm/MHz
and a maximum EIRP of 30 dBm. LPI requires client (STA) devices to have
a maximum PSD of -1 dBm/MHz. The maximum channel width is 320 MHz.
The following equation is used to calculate the EIRP from the PSD and
channel width:
EIRP = PSD + 10*log(channel width in MHz)
Using the maximum PSD values of 5 and -1 for APs and STAs respectively,
the EIRP in dBm for a given channel width can be calculated:
Channel Width (MHz) AP STA
------------------------------------------------
20 18 12
40 21 15
80 24 18
160 27 21
320 31 (max 30) 25 (max 24)
For channel widths up to 160 MHz, the maximum PSD is the limiting factor.
For the 320 MHz channel width, the maximum EIRP is the limiting factor.
Unfortunately, because there is currently no mechanism to specify
different power levels for AP and STA modes, and for different channel
widths, the smallest value has to be selected, which is 12 dBm. This
will likely cause connectivity problems with larger channel widths until
these additional parameters can be added.
6 GHz operation on oil platforms, vehicles, boats, trains, and drones is
prohibited except on commercial aircraft above 10,000 feet altitude.
An IR (Initiate Radiation) restriction is mentioned in the 6 GHz
specification.
Signed-off-by: Dennis Bland <dennis@dbperformance.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
With the 6 GHz band (U-NII-5, U-NII-6, U-NII-7, U-NII-8) in Canada, ISED
introduces the concept of a fixed PSD (Power Spectral Density) for all
supported 6 GHz channel widths. Wider channel widths have a higher noise
floor, therefore specifying a fixed PSD allows wider channels to
operate at a higher EIRP to maintain the same S/N ratio as smaller
channel widths.
Clause 4.6.2 requires non-client (AP devices to have a maximum PSD of 5
dBm/MHz and a maximum EIRP of 30 dBm. Clause 4.6.3 requires client (STA)
devices to have a maximum PSD of -1 dBm/MHz. Clause 4.4 specifies a
maximum channel width of 320 MHz. Clause 4.9 specifies indoor use only.
Operation on oil platforms, vehicles, boats, trains, and drones is
prohibited except on commercial aircraft above 10,000 feet altitude.
There is no IR (Initiate Radiation) restriction mentioned in the 6 GHz
specification.
The following equation is used to calculate the EIRP from the PSD and
channel width:
EIRP = PSD + 10*log(channel width in MHz)
Using the maximum PSD values of 5 and -1 for APs and STAs respectively,
the EIRP in dBm for a given channel width can be calculated:
Channel Width (MHz) AP STA
------------------------------------------------
20 18 12
40 21 15
80 24 18
160 27 21
320 31 (max 30) 25 (max 24)
For channel widths up to 160 MHz, the maximum PSD is the limiting factor.
For the 320 MHz channel width, the maximum EIRP is the limiting factor.
Unfortunately, because there is currently no mechanism to specify
different power levels for AP and STA modes, and for different channel
widths, the smallest value has to be selected, which is 12 dBm. This
will likely cause connectivity problems with larger channel widths until
these additional parameters can be added.
Signed-off-by: Dennis Bland <dennis@dbperformance.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
These were accidentally removed in the previous commit to release a new
regdb version. Add them back.
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Changes allowing lower portion of WiFi 6E spectrum. (5925-6425)
Amendment: https://www.legislation.gov.au/Details/F2022L00249
Full text: https://www.legislation.gov.au/Details/F2022C00281
Allows for both 250mW EIRP indoors or 25mW outdoors.
However, only the former limit is defined in this commit.
Signed-off-by: Richard Huynh <voxlympha@gmail.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
The rules lack spaces in the frequency range definition, which works
find for building the database but causes problems for some external
parsers. Add the missing spaces.
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
The Israeli Ministry of Communications has published an updated
revision of the normative radio band allocation table on 2021-03-29.
Notable change is the expansion of the range of allowed frequencies
in the 5GHz band.
v2: Increase bandwidth to 160MHz for 5470-5725 MHz range, as there is
no specified bandwidth limits in the document.
Signed-off-by: Roman Kunzman <roman.kunz@tutanota.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
In accordance with the EU Commision decision 2021/1067/EU the
Dutch Ministry of Economic Affairs and Climate Policy has opened
the use of the lower 6GHz spectrum, for indoor use, up to 23dBM (200mW).
NL Announcement https://zoek.officielebekendmakingen.nl/stcrt-2021-49492.pdf
NL Law: https://wetten.overheid.nl/BWBR0036378/2021-12-15
Unfortunately, only available in dutch.
Signed-off-by: Wilco Baan Hofman <wilco@baanhofman.nl>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
China had updated regulations on ISM frequencies by
"工信部无〔2021〕129号".
The new regulation effectives from Jan 1 2022.
Update regdb accroading to it's attachment "2400MHz、5100MHz
和 5800MHz 频段无线电发射设备射频技术要求".
Announcement: https://wap.miit.gov.cn/zwgk/zcwj/wjfb/tz/art/2021/art_e4ae71252eab42928daf0ea620976e4e.html
Attachment: https://wap.miit.gov.cn/cms_files/filemanager/1226211233/attach/20219/d125301b13454551b698ff5afa49ca28.pdf
Those documents are only available in Chinese.
Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
This patch is based on MSIT Public Notification 2021-86 ("Unlicensed Radio
Equipment Established Without Notice"), officially announced on 2021-11-29.
The PSD must not exceed 2.5 mW/MHz if the frequency range includes all or
part of 5230-5250 MHz and the bandwidth is equal to or less than 40 MHz.
This leads to the following:
* 5230-5250 @ 20 -> 17 dBm
* 5210-5250 @ 40 -> 20 dBm
Here the power limit for >20 MHz bandwidth is also lowered to 17 dBm, as
it's not possible to set different power limits for different bandwidths
at the moment.
Extend the last 5 GHz frequency range to 5850 MHz.
Wi-Fi 6E is now allowed with the following restrictions:
* Indoor: the full 1.2 GHz range, up to 160 MHz bandwidth and 2 dBm/MHz PSD
* Outdoor: the lower 500 MHz range, up to 160 MHz bandwidth and 25 mW EIRP
Here only the former entry is added.
And also update the regulatory source links.
Signed-off-by: Sungbo Eo <mans0n@gorani.run>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
This reverts commit 0d39f4cedf2d84dba5f9183f0dfb21cab23ac78a. I
accidentally applied the wrong version of this patch, so revert it in
order to apply the correct version.
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
Add WiFi 6E frequency band.
Sources:
(EU) 2021/1067: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32021D1067
BOE numero 308, de 24/12/202: Orden ETD/1449/2021: CNAF-2021 (page 302): https://www.boe.es/buscar/pdf/2021/BOE-A-2021-21346-consolidado.pdf
UN-167 RLANs en 6 GHz
Aplicaciones de uso común en la banda de 5945-6425 MHz.
De conformidad con la Decisión de Ejecución (UE) 2021/1067 de la Comisión, sobre el uso
armonizado de la banda 5945-6425 MHz para sistemas de acceso inalámbrico, incluidas las
redes de área local (WAS/RLAN), se permiten estas aplicaciones en la citada banda de
frecuencias bajo la consideración de uso común con arreglo a las condiciones técnicas
indicadas en el anexo a la citada Decisión.
Los dispositivos de baja potencia para uso en interiores (LPI), tendrán una potencia máxima
de 23 dBm (p.i.r.e.), con una densidad de potencia p.i.r.e. media máxima de 10 dBm/MHz
para las emisiones en banda y de -22 dBm/MHz para emisiones fuera de banda.
Los dispositivos de muy baja potencia para uso en interiores y en exteriores (VLP), tendrán
una potencia máxima de 14 dBm (p.i.r.e.), con una densidad de potencia p.i.r.e. media
máxima de 1 dBm/MHz para emisiones en banda, o hasta 10 dBm/MHz si funcionan con
canalización que no supere los 20 MHz, y de -45 dBm/MHz para emisiones fuera de banda.
En cualquier caso, estos dispositivos deberán utilizar técnicas de acceso al espectro y
mitigación de interferencias que garanticen los requisitos esenciales de la Directiva
2014/53/UE.
Cc: Seth Forshee <sforshee@kernel.org>
Cc: WIRELESS ML <linux-wireless@vger.kernel.org>
Cc: REGDB ML <wireless-regdb@lists.infradead.org>
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
802.11ah does not have a band which intersects global
regulatory domains, so just add the possible range as
NO-IR to at least allow passive scan.
Signed-off-by: Thomas Pedersen <thomas@adapt-ip.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
The 902-928MHz band is one of the US ISM bands, so follows
the same emission limits described in FCC part 15.
Signed-off-by: Thomas Pedersen <thomas@adapt-ip.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
The French national agency for radio frequencies (ANFR) has published an updated
revision of the normative radio band allocation table on 2021-12-14. It includes
the authorization for the lower 6 GHz band for 802.11ax as prescribed by the EU
2021/1067 decision, as well as the authorization for channels 5 and 6 in the 60
GHz band for 802.11ay.
The declaration for the 6 GHz band follows the Low Power Indoor constraints.
https://www.anfr.fr/fileadmin/mediatheque/documents/tnrbf/TNRBF_2021-12-14.pdf
Signed-off-by: Romain Izard <romain.izard.pro@gmail.com>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
This patch is based on MSIT Public Notification 2021-86 ("Unlicensed Radio
Equipment Established Without Notice"), officially announced on 2021-11-29.
The PSD must not exceed 2.5 mW/MHz if the frequency range includes all or
part of 5230-5250 MHz and the bandwidth is equal to or less than 40 MHz.
This leads to the following:
* 5230-5250 @ 20 -> 17 dBm
* 5210-5250 @ 40 -> 20 dBm
Here the power limits for 80/160 MHz bandwidth are also lowered to 17/20 dBm,
as it's not possible to set different power limits for different bandwidths
at the moment.
Extend the last 5 GHz frequency range to 5850 MHz.
WiFi 6E is now allowed with the following restrictions:
* Indoor: the full 1.2 GHz range, up to 160 MHz bandwidth and 2 dBm/MHz PSD
* Outdoor: the lower 500 MHz range, up to 160 MHz bandwidth and 25 mW EIRP
Here only the latter entry is added.
And also update the regulatory source links.
Signed-off-by: Sungbo Eo <mans0n@gorani.run>
|
|
In accordance with the EU Commision decision 2021/1067/EU the
Croatian Regulatory Authority for Network Industries (HAKOM)
has issued the general license for usage of the 5945-6425 MHz
spectrum for 6GHz VLPI and LPI devices in OD-236 and OD-237.
They have the same restrictions as in EU countries which already
implemented the decision earlier.
OD-236: https://www.hakom.hr/UserDocsImages/op%C4%87e%20dozvole%20prosinac%202009.g/Opca_dozvola_236.pdf
OD-237: https://www.hakom.hr/UserDocsImages/op%C4%87e%20dozvole%20prosinac%202009.g/Opca_dozvola_237.pdf
Unfortunatelly, both licenses are available only in Croatian.
Signed-off-by: Robert Marko <robert.marko@sartura.hr>
Signed-off-by: Seth Forshee <sforshee@kernel.org>
|
|
According to 47 CFR § 15.407(a)(2), the U-NII-2A (5.25-5.35 GHz) and
U-NII-2C (5.47-5.725 GHz) DFS bands are subject to the following [1]:
"For the 5.25-5.35 GHz and 5.47-5.725 GHz bands, the maximum conducted
output power over the frequency bands of operation shall not exceed
the lesser of 250 mW or 11 dBm + 10 log B, where B is the 26 dB
emission bandwidth in megahertz."
As such, increase the TX power limit for the U-NII-2A and U-NII-2C DFS
bands to 250 mW (24 dBm) to match the FCC's current rules. These power
limits have remained unchanged since the § 15.407 amendment by the FCC
in 2014 [2].
[1] https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-15/subpart-E/section-15.407#p-15.407(a)(2)
[2] https://www.federalregister.gov/d/2014-09279/p-131
Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
Signed-off-by: Seth Forshee <sforshee@kernel.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>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Handy to find modifications or new rules.
Cc: José Daniel Rodríguez <josedanielr@yandex.com>
Cc: Seth Forshee <seth.forshee@canonical.com>
Cc: WIRELESS ML <linux-wireless@vger.kernel.org>
Cc: REGDB ML <wireless-regdb@lists.infradead.org>
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Based on the current resolution on the use of wireless networks available at:
https://www.mincom.gob.cu/sites/default/files/marcoregulatorio/r_98-19_reglamento_redes_inalambricas.pdf
Signed-off-by: Jose Daniel Rodriguez <josedanielr@yandex.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
gen-pubcert.sh hardcodes the 'sforshee' common name when generating the
certificate. Make it depend on REGDB_AUTHOR instead, which defaults to
$(whoami).
Signed-off-by: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
This patch is based on the latest Ukrainian norms https://zakon.rada.gov.ua/laws/show/z0201-15#n48.
* Extend some frequency ranges.
* Increase EIRP of frequency ranges.
* Set wmmrule=ETSI to frequency ranges that are related to EN 301 893.
* Permit outdoor usage of 2.4 GHz band channels.
* Prohibit outdoor usage of some 5 GHz band channels.
Signed-off-by: Illia Volochii <illia.volochii@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Cc: Seth Forshee <seth.forshee@canonical.com>
Cc: WIRELESS ML <linux-wireless@vger.kernel.org>
Cc: REGDB ML <wireless-regdb@lists.infradead.org>
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Based on [1]:
* Extend 2400-2483.5 MHz range
* 5150–5250 MHz range may be up to 200 mW
* Add 5725-5850 MHz range for indoor usage
* Add 57-66 GHz range.
* In 5470-5725 range change the bandwidth from 80 to 160
[1] http://adilet.zan.kz/rus/docs/V1500010730
Signed-off-by: Pavel Starosek <starosekpd@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Based on [1], the 5.8 GHz limit for GB is 200 mW and requires DFS
and TPC. Update the rule accordingly.
While at it, expand the 5470 - 5725 rule to 5730 as specified in
the same document to allow channel 144 to be used.
[1] https://www.ofcom.org.uk/__data/assets/pdf_file/0028/84970/ir-2030.pdf
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Update range to 5.725 - 5.875 Ghz
as mentioned at https://fab.gov.pk/type-approval/
Signed-off-by: Abdul Rauf <abdulraufmujahid@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Croatian Regulatory Authority for Network Industries (HAKOM) has
updated the general licenses OD-85 and OD-86 with the new OD-85a
and OD-86a versions.
These introuduce the following changes:
* Outdoor usage for 5150-5250 and 5250-5350 MHz ranges is permitted
* 5150-5250 MHz range TPC requirment was dropped and power output raised to 200mW
OD-85a: https://www.hakom.hr/UserDocsImages/op%C4%87e%20dozvole%20prosinac%202009.g/Opca_dozvola_85a.pdf
OD-86a: https://www.hakom.hr/UserDocsImages/op%C4%87e%20dozvole%20prosinac%202009.g/Opca_dozvola_86a.pdf
Signed-off-by: Robert Marko <robert.marko@sartura.hr>
Cc: Luka Perkov <luka.perkov@sartura.hr>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The precisely allowed transmission power on channel 12 & 13 is not clear.
I did some fact checking and document reviews in the past, but still
failed to come up with an exact reference or calculation regarding what TX
power should be allowed in general to reduce interference in the
neighboring restricted band 2483.5-2500 MHz and whether indoor vs. outdoor
and b/g/n modulation would make a difference (probably yes).
Existing documents that discuss this are vague and pretty much out of date:
https://en.wikipedia.org/wiki/List_of_WLAN_channels#endnote_B
Following these guidelines, I failed to come up with an approximate
formula that would prohibit usage of channel 12 & 13, but still allow
usage of channel 11 with full power, hence at least part of the argument
for prohibiting channel 12 & 13 needs to be refined.
Until further research, just to stay safe, I propose that we restore the
previous limitation of disabling channel 12 & 13 as before. We should
work towards finding a safe transmission power to use on both and specify
that (like 50mW on channel 13 and 100mW on channel 12?).
I've also started a discussion for investigation on Wikipedia:
https://en.wikipedia.org/wiki/Talk:List_of_WLAN_channels#Should_the_2.4GHz_channel_12_and_13_in_the_USA_need_updating?
Signed-off-by: bkil <b.K.il.h.u+tigbuh@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Update the rules to the frequency ranges and power limits
documented in [1], and update 5GHz rules to comply with
EN 301 893.
[1] https://www.tra.gov.eg/en/industry/importing-of-equipment/Pages/Regulations-for-use-of-Wireless-Networks-Devices.aspx
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The bands are wider and more continuous:
5.15-5.35 GHz, 5.47-5.725 GHz and 5.725-5.85 GHz.
Based on the April 2, 2020 version of e-CFR Title 47 Part 15,
Radio Frequency Devices.
This also includes a small tweak for channel 144 similar to TW.
Signed-off-by: bkil <b.K.il.h.u+tigbuh@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
OFCOM extended the DMG band to include till 71GHz.
Signed-off-by: Chaitanya Tata <chaitanya.mgit@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Add 802.11ad 60GHz band:
https://www.imda.gov.sg/-/media/Imda/Files/Regulation-Licensing-and-Consultations/ICT-Standards/Telecommunication-Standards/Radio-Comms/IMDATSSRD.pdf
Changes to IDA TS SRD, Issue 1 Rev 4, Jul 09 - Table 1 (31):
"The band 57 - 66 GHz at <=10W (e.i.r.p) is an additional frequency allocation for Wireless LAN / broadband access applications."
Harmonize 5470-5725MHz band non-TPC transmit power with other FCC Part 15 Section 15.407 and EN 301 893 domains (AU, BG)
Patch v2: 5150-5250MHz does not need to observe TPC thus remains at 23dBm
Signed-off-by: Andrew Yong <me@ndoo.sg>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Update based on new regulations released in April 2019:
https://jdih.kominfo.go.id/produk_hukum/view/id/676/t/peraturan+menteri+komunikasi+dan+informatika+nomor+1+tahun+2019+tanggal+24+april+2019
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Various changes in the commit mentioned below broke
compatibility with python2. Restore it in a way that
makes it worth with both versions.
Fixes: f3c4969c2485 ("wireless-regdb: make scripts compatible with Python 3")
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Russian entry is incorrect. According to the last regulations
document of Feb 29, 2016, 160 MHz channels and 802.11ad are allowed.
http://rfs-rf.ru/upload/medialibrary/c1a/prilozhenie-1-k-resheniyu-gkrch-_-16_36_03.pdf
Note that there was never a DFS requirement in Russia, but always was
NO-OUTDOOR on 5GHz.
Maximum power is 200mW that is ~23dBm on all 5GHz channels.
Also Russia has never been regulated by ETSI.
EIRP has been reduced by 4dBm because of TPC requirement.
Signed-off-by: Dmitry Tunin <hanipouspilot@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
This patch unites entries for CEPT countries according
https://www.ecodocdb.dk/download/25c41779-cd6e/Rec7003e.pdf
(CEPT ERC Recommendation70-03, Edition of June 2019) which lists all
CEPT countries, who has harmonized those standards.
The most important (definition) entries are:
Table 1 / rows i and j (SRDs for 2.4 and 5GHz bands)
Table 3 / row b (2.4 GHz band)
Table 14 / rows e1, e2 and f (5GHz bands)
and Appendix 1 - National implementation
with sub-tables and rows representing implementation of above standards:
ANNEX 1: NON-SPECIFIC SHORT RANGE DEVICES
Annex i: 2400-2483.5 MHz
Annex j: 5725-5875 MHz
ANNEX 3: WIDEBAND DATA TRANSMISSION SYSTEMS
Annex b: 2400-2483.5 MHz
ANNEX A: INFORMATIVE ANNEX COVERING THE APPLICATIONS OPERATING UNDER
GENERAL AUTHORISATION...
Annex e1: 5150-5350 MHz ECC/DEC/(04)08
Annex e2: 5470-5725 MHz ECC/DEC/(04)08
Annex f: 5875-5905 MHz ECC/DEC/(08)01
Signed-off-by: Emil Petersky <emil.petersky@streamunlimited.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
This patch unites entries for EU countries, as they have been harmonized
latest by July 2014...
EU decision 2005/513/EC:
https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02005D0513-20070213
EU decision 2006/771/EC:
https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02008D0432-20080611
Signed-off-by: Emil Petersky <emil.petersky@streamunlimited.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
This range ends at 5725 MHz, but channel 144 extends to 5730 MHz.
The Linux kernel however does not seem capable of considering them
most restrictive subset of multiple rules.
Since 5725 ~ 5730 MHz belongs to the next range which has looser
requirements, we can do this manually and extend the range by 5 MHz
to make the kernel happy and be able to use channel 144.
Also, looking at the US regulations, which the TW ones are based on,
The DFS range ends at 5730 MHz, while the next range starts at 5735
MHz. This doesn't match the actual regulations, but is skewed to meet
wireless channel boundaries. I prefer the database match the law,
and be adjuested only if necessary.
Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The commit referenced below changes the 5GHz frequency range 5250-5330
to 5150-5330, making that range overlapping with the existing range
5170-5250. This imposes DFS limitations and a reduced maximum power
level for the range 5170-5250.
The change of the frequency range seems not intentional. Instead the
commit should have changed the 5170-5250 range to 5150-5250, and the
5250-5330 range to 5250-5350 (see [1]).
[1] https://www.ofcomnet.ch/api/rir/1010/05
Fixes: 957a7cff72a3 ("wireless-regdb: update regulatory rules for Switzerland (CH), and Liechtenstein (LI) on 5GHz")
Signed-off-by: Martin Willi <martin@strongswan.org>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The official documents are not feely available, but based on
summaries such as [1] and numerous third-party resources the 60
GHz band in Japan has been 57-66 GHz for some time now. Update
our rules accordingly.
[1] https://webstore.arib.or.jp/en/products/detail.php?product_id=288
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Cc: Seth Forshee <seth.forshee@canonical.com>
Cc: WIRELESS ML <linux-wireless@vger.kernel.org>
Cc: REGDB ML <wireless-regdb@lists.infradead.org>
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Update power limit as documented in:
http://www.law.go.kr/%ED%96%89%EC%A0%95%EA%B7%9C%EC%B9%99/
%EC%8B%A0%EA%B3%A0%ED%95%98%EC%A7%80%EC%95%84%EB%8B%88%ED
%95%98%EA%B3%A0%EA%B0%9C%EC%84%A4%ED%95%A0%EC%88%98%EC%9E
%88%EB%8A%94%EB%AC%B4%EC%84%A0%EA%B5%AD%EC%9A%A9%EB%AC%B4
%EC%84%A0%EA%B8%B0%EA%B8%B0/(2018-89,20181227)
which revised on December 27, 2018.
Signed-off-by: Peter Oh <peter.oh@bowerswilkins.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
According to multiple sources channels 8-16 (5030-5090MHz) were only
allowed in Japan until Nov-30, 2017 (later extended to Nov-30, 2018).
https://www.tele.soumu.go.jp/j/adm/system/trunk/wimax/5ghz/index.htm
http://www.dspr.co.jp/wp/wp-content/uploads/2017/10/The-expiration-date-of-some-frequency-of-the-5GHz-band-radio-access-system_eng.pdf
Signed-off-by: Vladimir Koutny <vladimir.koutny@streamunlimited.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Cc: Seth Forshee <seth.forshee@canonical.com>
Cc: WIRELESS ML <linux-wireless@vger.kernel.org>
Cc: REGDB ML <wireless-regdb@lists.infradead.org>
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Add new frequency ranges, increase power, as documented in:
http://wpc.dot.gov.in/WriteReadData/userfiles/License%20Exemption%20in%205%20GHz%20G_S_R_1048(E)%20dated%2022nd%20October,%202018.pdf
Signed-off-by: Felix Fietkau <felix@wiowireless.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
In reference to the current "Regulations on exemptions from the
licence obligation for certain radio transmitters" issued by
the Swedish Post and Telecom Authority (PTS) on 18 Sep 2018
and valid from 1 Nov 2018 [1]:
* 2400-2483.5M: extend bounds (§ 154)
* 5150-5250M: extend bounds, add NO-OUTDOOR, no TPC so +3dB (§ 162)
* 5250-5350M: extend bounds, add NO-OUTDOOR (§ 162)
* 5470-5725M: extend bounds (§ 164)
* 5725-5875M: introduce; EU SRD provisions have been implemented (§ 166)
* 57-66G: add NO-OUTDOOR (§ 202)
[1] https://pts.se/globalassets/startpage/dokument/legala-dokument/foreskrifter/radio/beslutade_ptsfs-2018-3-undantagsforeskrifter.pdf
Signed-off-by: Peter Lundkvist <peter.lundkvist@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Include channels 4, 5 & 6 for US in 60GHz band. FCC extended the
57-64GHz band till 71GHz with almost same rules.
Signed-off-by: Chaitanya Tata <Chaitanya.Tata@bluwireless.co.uk>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
According to [1], SRD devices in this range are allowed in Portugal, as
specified in this document (page 56), and in compliance with ETSI EN 300 440-1.
[1] https://www.anacom.pt/streaming/25.5_10.000mhz.pdf?contentId=271706&field=ATTACHED_FILE
Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Cc: Seth Forshee <seth.forshee@canonical.com>
Cc: WIRELESS ML <linux-wireless@vger.kernel.org>
Cc: REGDB ML <wireless-regdb@lists.infradead.org>
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
d46d731c made it obsolete.
Cc: Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: Seth Forshee <seth.forshee@canonical.com>
Cc: WIRELESS ML <linux-wireless@vger.kernel.org>
Cc: REGDB ML <wireless-regdb@lists.infradead.org>
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Commit 8607edfdb6568 ("wireless-regdb: Parse wmm rule data") introduced
a dependency to the python module attr which is not included by default
in all python installations. Replace the code with manually coding the
constructor instead of using attr. This makes the code also work on
systems without attr.
I would like to avoid an additional dependency in OpenWrt where we
compile the regulatory database inside of the build system.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The documents
https://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf
and
https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/2010_07_WLAN_5GHz_pdf.pdf
show that the limits for the 5GHz bands are out of date:
* 5150 - 5250 MHz only usage is allowed to use up to 23 dBm (200 mW) even
without TPC
Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The documents
https://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf
and
https://www.anfr.fr/fileadmin/mediatheque/documents/controle/20171127ANFR_-_ficheRLAN_5GHz.pdf
show that the limits for the 5GHz bands are out of date:
* frequencies don't match the official limits
* 5150 - 5350 MHz is not for outdoor usage
* 5150 - 5250 MHz only usage is allowed to use up to 23 dBm (200 mW) even
without TPC
Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Cc: Seth Forshee <seth.forshee@canonical.com>
Cc: WIRELESS ML <linux-wireless@vger.kernel.org>
Cc: REGDB ML <wireless-regdb@lists.infradead.org>
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Liechtenstein (LI) on 5GHz
Update to reflect the current data published in the 'National Frequency
Allocation Strategy Table' [0] for Switzerland and Liechtenstein, which
at the time of writing points to the documents [1] and [2].
[0] https://www.ofcomnet.ch/#/fatTable
[1] https://www.ofcomnet.ch/api/rir/1010/05
[2] https://www.ofcomnet.ch/api/rir/1010/04
Signed-off-by: Henrik Laxhuber <henrik@laxhuber.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Viestintävirasto 15 AM/2018 M
Section 10 Non-specific short range devices
https://www.finlex.fi/data/normit/32670/Regulation_15AM.pdf
Signed-off-by: Jukka Pirinen <jukka.pirinen@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
* 2400-2483.5M: extend bounds
* 5150-5250M: extend bounds, add NO-OUTDOOR, no TPC so +3dB
* 5250-5350M: extend bounds, add NO-OUTDOOR
* 5470-5725M: extend bounds
* 5725-5875M: introduce, as EU SRD provisions have been implemented
* 57-66G: add NO-OUTDOOR
Freely available online references have been added hosted by the regulatory
body in Hungary, the National Media and Infocommunications Authority.
To refer to a specific section, you can grep for the frequency in question.
Translation key:
"Csak beltéri" / "Épületen belüli használatra korlátozott" = indoor only;
"Kültéri és beltéri" = both indoor and outdoor;
"Nem működő TPC esetén a maximális teljesítményjellemzők 3 dB-lel
csökkennek." = reduce max power specs by 3dB in case of no TPC;
"Rögzített kültéri telepítés nem megengedett" = no fixed outdoor install
Signed-off-by: bkil <b.K.il.h.u+tigbuh@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The power limit should be 25 mW and not 25 dBm. Thanks to
Christian Sünkenberg for pointing out the mistake.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The iteration in this function is over countries.itervalues(),
which is not compatible with python 3. Switch to iterating over
contries.values() instead.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Python 3 gives errors as a result of the changes to add wmm
rules since Permission.wmmrule can be set to None:
TypeError: '<' not supported between instances of 'WmmRule' and 'NoneType'
To fix this, supply compairson methods for WmmRule instead of
using the ones provided by attrs. Doing this means we also need
to supply a __hash__ method.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Updates are based on the information in
http://www.asep.gob.pa/images/telecomunicaciones/Anexos/PNAF-dic2015.pdf.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Based on [1] and [2], use of short range devices in this range
is now permitted in France. Add a rule for this range, using the
power limit of 25 dBm as specified in these documents and in
ETSI EN 300 440.
[1] https://www.arcep.fr/uploads/tx_gsavis/14-1263.pdf
[2] https://www.arcep.fr/uploads/tx_gsavis/14-1263.pdf
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Add code to parse wmm rule data.
Also write it to the the regulatory.db fw file
Signed-off-by: Haim Dreyfuss <haim.dreyfuss@intel.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The ETSI EN 301 893 v211 (2017-05) standard defines a new channel
access mechanism that all devices (WLAN and LAA) need to comply with.
In previous versions the device was allowed by ETSI to implement
802.11 channel access mechanism based on a set of priority classes
which are taken from 802.11.
According to the new standard there might be some exception
which require the EEA and the EFTA countries, which adhere
ETSI rules, to follow more restrictive rules.
In order to comply with the new standard introduced by ETSI, add
wmmrule global item with the new ETSI channel mechanism rules.
Also add wmmrule flag to EEA and EFTA countries.
Signed-off-by: Haim Dreyfuss <haim.dreyfuss@intel.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
When playing with the generation scripts for OpenWrt development, I noticed
that these scripts still required Python 2. Future-proof them by replacing
deprecated functions with new Python 3 compatible variants. The result
works with both Python 2.7 and Python 3.x; older Python 2.x releases are
not supported anymore.
regulatory.db and regulatory.bin are unchanged and reproducible across
Python versions. Note that there is no stable release of m2crypto for
Python 3 yet; I used the current development branch for testing.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The iteration order of dicts varies across Python implementations, in
particular Python 2 and 3. Fully sort key lists rather than only taking
the "freqband" field into consideration to make the build of the binary
regdbs fully reproducible.
This commit changes the order of the entries in the generated files; the
output of regdbdump is unchanged.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Add information about regulatory.db to the regulatory.bin man
page, and alias the regulatory.db man page to refer to the page
for regulatory.bin.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
regulatory.db is being installed to the CRDA path, however the
kernel expects it to be in /lib/firmware. Install it to the
proper location. Also install the detached signature, which is
needed for the kernel to check verify the database authenticity.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The current makefile rule for the public certificate calls for an
openssl config file which is not provided. Let's put the pubcert
generation into a script named gen-pubcert.sh and embed the
openssl configuration file there.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Add a x509 certificate for sforshee.key.pub.pem. This is the same
certificate which is shipped in the kernel for validating
regulatory database files.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Johannes removed generation and installation of these files when
adding support for the new database format. We need to keep
generating these files to support distros still using CRDA, so
restore support for building and installing these files in the
makefile.
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
TODO: clean up the Makefile stuff ...
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Refresh the frequency ranges and power limits based on the
following sources:
https://erhvervsstyrelsen.dk/sites/default/files/007_interface-datanet_5-6_ghz.pdf.pdf
https://erhvervsstyrelsen.dk/sites/default/files/radiograenseflader-63.pdf
Cc: Per Mejdal Rasmussen <pmr@its.aau.dk>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Add rules for 5150-5250 MHz, 5250-5350 MHz, and 5470-5725 Mhz
based on the documents at [1] and [2].
v2: Also add DFS region
[1] http://mic.gov.kz/sites/default/files/pages/pravila_prisvoeniya_polos_chastot_no34.pdf
[2] http://adilet.zan.kz/rus/docs/P000001379_
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
UN - 130 Dispositivos de corto alcance en 5 GHz :
https://www.boe.es/buscar/act.php?id=BOE-A-2013-4845&tn=1&p=20150410
Cc: Seth Forshee <seth.forshee@canonical.com>
Cc: linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
certification-requested "20mW" (13dBm).
Signed-off-by: Andreas Mohr <andim2@users.sf.net>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Based on the information from [1] the power limit for 5170-5250 Mhz
can be increased. Additionally 5170-5330Mhz are restricted to indoor
use.
There are references to e.i.r.p density in [1] that will affect the
power available for wide channels, but they are not reflected in
this change as it's unclear how they would be specified.
[1] https://www.btk.gov.tr/File/?path=ROOT%2f1%2fDocuments%2fOrdinance%2fBY%2DLAW%20ON%20SHORT%20RANGE%20DEVICES.pdf
Signed-off-by: Edwin Steele <edwin@wordspeak.org>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
2.4GHz and the lower 5GHz band can now be use with up to 23dBm. But the DFS
channels in general require TPC to be usable. Only 5150 - 5250 has an
exception which allows the use of it without TPC when reducing the power to
20 dBm.
Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The latest low power radio frequency devices technical regulations [1]
released by Taiwan's regulatory body, NCC, opens up 57 GHz ~ 66 GHz to
most devices, including WiGig.
[1] LP0002 Low-power Radio-frequency Devices Technical Regulations 2016/8/23
http://www.ncc.gov.tw/english/show_file.aspx?table_name=news&file_sn=681
Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Taiwan's Ministry of Transportation and Communications updated its
frequency allocation rules again on 2017/02/22. The amended articles
are not related to this database, but the link should be kept up to
date, as the old one is no longer accessible.
Taiwan's regulatory body, NCC, published its updated technical
regulatory standard for low-power radio frequency devices, LP0002.
The URL has not changed. The new standard opens up more bandwidth
for 5g U-NII WiFi and 60g WiGig devices. Transmission power for
5.25 ~ 5.35 GHz is also increased, but this was already covered
in commit 9a618d9b5fb2 ("wireless-regdb: Update 5 GHz rules for
Taiwan (TW) to follow US").
This patch updates the link and comments for the rules and standards,
and also adds inline comments referencing the governing section of the
LP0002 standard for each band.
Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
wireless-db: Update rules for Canada 5ghz to add NO-OUTDOOR
According to [1] Canada requires NO-OUTDOOR to set be on 5150 to 5250
[1] http://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf10971.html Section 6.2.1
Signed-off-by: Aron Rosenberg <arosenberg@logitech.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Sourced from the current legislation at
https://www.legislation.gov.au/Details/F2016C00432
The current rules exceed legal limits between 5250-5330MHz, and permit
illegal operation in 5600-5650MHz (disallowed regardless of DFS).
Frequency ranges and EIRP limits for all ranges have been updated to
match items 59-63, 65 in the linked document. As the rules for AU have
never previously mirrored local regulations, changes include a
significant increase in the allowable 2.4GHz EIRP and smaller increases
in most other bands.
In order to allow 80MHz operation between 5650-5730MHz (bordering two
bands) the lower, more restrictive band has been rounded up by 5MHz.
Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Based on the information from [1] the power limit for 5150-5250
MHz can be increased to 23 dBm. Also update some rules to match
exact frequency ranges given in that document.
[1] http://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf10971.html
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The "Indoor Use of low power wireless equipment in the frequency band 5
GHz (Exemption from Licensing Requirement) Rules, 2005" notification by
Ministry of Communications and Information Technology (Wireless Planning
and Coordination Wing) (New Delhi, the 28th January 2005) does not
mandate use of DFS, so remove the DFS flag from the 5250-5330 MHz band
in India.
In addition, increase the TX power limit to 23 dBm to match the 200 mW
maximum mentioned in the same notification. Also use the exact ranges
from that notification and enable use of 160 MHz channels in the
5150-5350 MHz band.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Add 60GHz regulatory rules for Korea (KR).
Source is
http://www.law.go.kr/%ED%96%89%EC%A0%95%EA%B7%9C%EC%B9%99/%EB%AC%B4%EC%84%A0%EC%84%A4%EB%B9%84%EA%B7%9C%EC%B9%99
Signed-off-by: Maya Erez <qca_merez@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The "Frequenznutzungsplan" is not really a good reference as it's
a list of all frequency allocations and does only list basic
information about the allocation. This patch changes the comments
to reference directly the corresponding documents which provide
all information about the allocation.
This patch does only change comments, all entries have been left
unchanged. However the entries have been verified to match the
mentioned documents.
Signed-off-by: Maximilian Engelhardt <engelhardt@perisens.de>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Make sure the rules reflect exatly the contents of the List of Radio
Equipment That Uses Harmonized Within the European Union Bands and
Electronic Communications Terminal Equipment[1], add proper references
and document the power reduction in the 5250-5350 MHz and 5470-5725 MHz
bands with a note.
[1] http://www.crc.bg/files/_bg/Spisak_2015.pdf
Signed-off-by: Petko Bordjukov <bordjukov@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Below the patch to include SRD as per ETSI EN 300 440-1
for NL.
Signed-off-by: Anne Marcel Roorda <marcel@slowthinkers.net>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
In Europe ETSI standardized the used for short range devices
(SRD) [1] in ETSI EN 300 440-1 [2]. According to this standard
generic use equipment is allowed to transmit in the frequency
range form 5725 MHz to 5875 MHz with a maximum output power of 25
mW e.i.r.p. This generic allocation also allows transmission of
802.11 devices.
[3] has a list of countries and their status about the
implementation of the SRD frequency bands. For the 5 GHz band
this can be seen on page 38 in the paragraph ANNEX 1 and the
entry Annex j.
Attached is a patch that adds the 5 GHz SRD band to db.txt for
Germany.
[1] http://www.etsi.org/technologies-clusters/technologies/radio/short-range-devices
[2] http://www.etsi.org/deliver/etsi_en/300400_300499/30044001/01.06.01_60/en_30044001v010601p.pdf
[3] http://www.erodocdb.dk/Docs/doc98/official/pdf/REC7003e.pdf
Signed-off-by: Maximilian Engelhardt <engelhardt@perisens.de>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Resolución 127, 2011 - Reglamento Banda 2,4 GHz.:
http://www.mincom.gob.cu/sites/default/files/marcoregulatorio/R%20127-11%20Reglamento%20banda%202,4%20GHz.pdf
Cc: Seth Forshee <seth.forshee@canonical.com>
Cc: linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Back in 2012, in commit 6d87df6f9657 ("regdb: allow 40 MHz on world
roaming channels 12/13") I evidently broke the world regulatory data
to the point where it was always discarded by the kernel because the
40 MHz bandwidth doesn't fit into the rule range.
Around the same time, I updated the in-kernel regulatory domain with
the same mistake, but unlike the userspace data, the in-kernel data
isn't actually checked for validity.
The end result was that the (inconsequentially invalid) data in the
kernel was always used because the userspace data was rejected.
Fix this by changing the rule to 20 MHz and adding the AUTO-BW flag.
It seems that Janusz had made a similar change in commit 5cfc8073ce35
("wireless-regdb: set AUTO bandwidth for world regulatory"), but it
was reverted for unknown reasons a little less than half a year later
(commit cfa3734b11b2).
The kernel uses very similar invalid rules, but it never checks them
for validity and just uses them, so HT40- ends up getting enabled on
these channels. Thus, when the kernel requests the world regdomain
from userspace, gets the invalid data and rejects it, it falls back
to using the built-in data which is very similar and not validated.
I've tested this now, and the ruleset is now accepted by the kernel
and results in the correct data.
This also means that Jouni's 160 MHz fixes were inconsequentialy and
only the corresponding kernel changes could have been used.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Bands in 5150-5350 MHz are limited to indoor use, and band 5150-5250 MHz
has an increased power limit. The ranges are also slightly expanded to
match the regulation.
Regulatory source (6 Feb 2015), Section 13:
https://www.viestintavirasto.fi/attachments/maaraykset/Viestintavirasto15AH2015_en.pdf
Verified also from the authoritative Finnish version:
https://www.viestintavirasto.fi/attachments/maaraykset/Viestintavirasto15AH2015M.pdf
Signed-off-by: Anssi Hannula <anssi.hannula@iki.fi>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Update frequency allocation rules to mach data from table [1].
Also increase allowed power limit for range 5150-5250 Mhz to 200mW.
[1] http://tablice.hakom.hr:8280/vis?lang=en
Signed-off-by: Andrej Vlasic <andrej.vlasic0@gmail.com>
(saf: Use dBm instead of mW for power limits)
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
There's no "g" prefix, only "G" (1e9) that was clearly intended here.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
|
|
This extends regulatory rules for Greenland to allow 160 MHz VHT
channels. This was missed in the earlier set of patches that added 160
MHz for large number of countries.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Following the amendment of FCC part 15E and U-NII regulations effective
2014/06/02, and the opening up of 5150 ~ 5250 MHz and 5600 ~ 5650 MHz
spectrum in Taiwan, vendors have asked whether Taiwan's regulations
would be updated to match the new FCC rules, when this would happen,
and what to do in the interim.
The NCC, Taiwan's regulatory body has officially replied that new
amendments are under way, and the goal is to match the FCC rules.
Until the amendments come through, vendors are free to test and
submit applications using the new FCC rules for transmission power
limits and DFS requirements, though unintended / unwanted emissions
must still conform to the current standard, LP0002. [1][2]
This has been confirmed via a phone call to the NCC.
[1] http://www.rheintech.com/our-blog/item/585-taiwan-ncc-opens-5150-5250-mhz-for-wireless-devices
[2] Proposal #10312260 (p.6, Chinese),
http://www.etc.org.tw/_library/K00/%E9%9B%BB%E4%BF%A1%E7%B5%82%E7%AB%AF%E8%A8%AD%E5%82%99%E5%AF%A9%E9%A9%97/1031223_nccqa56.pdf
Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Taiwan's Ministry of Transportation and Communications revised its
frequency allocation rules [1] on 2014/11/17, opening up 5150 ~ 5250
MHz to U-NII applications.
Taiwan's regulatory body, NCC, officially stated [3][4] that until
the technical regulatory standard [2] are updated to cover this part
of the spectrum, FCC rules (part 15E, 15.407, effective 2014/06/02)
shall serve in its place.
Also add AUTO-BW to this and the next (5250 ~ 5350 MHz) rule, so the
system can actually use VHT160 channels spanning these two rules.
[1] http://www.motc.gov.tw/websitedowndoc?file=post/201411171137330.doc&filedisplay=Table+of+radio+frequency+allocation.doc
[2] http://www.ncc.gov.tw/english/show_file.aspx?table_name=news&file_sn=681
[3] http://www.rheintech.com/our-blog/item/585-taiwan-ncc-opens-5150-5250-mhz-for-wireless-devices
[4] Proposal #10312260 (p.6, Chinese),
http://www.etc.org.tw/_library/K00/%E9%9B%BB%E4%BF%A1%E7%B5%82%E7%AB%AF%E8%A8%AD%E5%82%99%E5%AF%A9%E9%A9%97/1031223_nccqa56.pdf
Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The FCC increased the maximum conducted transmission power for the
U-NII-1 (5150 ~ 5250 MHz) band to 30 dBm or 1 W for master devices
and 24 dBm or 250 mW for mobile/portable
devices.
Since 250 mW is slightly lower than 24 dBm, set the power limit to
a conservative value of 23 dBm.
Effective 6/2/2014.
See FCC KDB 905462 D06.
Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Taiwan's frequency allocation rules [1] list the following frequency
ranges available for low power RF devices:
- 2400 ~ 2483.5 MHz
- 5150 ~ 5250 MHz
- 5250 ~ 5350 MHz
- 5470 ~ 5725 MHz
- 5725 ~ 5850 MHz
Update the rules to match. Since 5250 ~ 5350 MHz is wide enough for
VHT80, and there are no regulations against it, enable it as well.
[1] http://www.motc.gov.tw/websitedowndoc?file=post/201411171137330.doc&filedisplay=Table+of+radio+frequency+allocation.doc
[2] http://www.ncc.gov.tw/english/show_file.aspx?table_name=news&file_sn=681
Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Taiwan's Ministry of Transportation and Communications revised its
frequency allocation rules [1] on 2014/11/17, allowing usage of 5600 ~
5650 MHz, previously allocated to weather radars, to U-NII applications
with DFS support.
Also, the technical regulations [2] show that for 5470 ~ 5725 MHz U-NII
applications, the peak transmit power shall not exceed the lesser of
250 mW (slightly less than 24 dBm) or 11 dBm + 10log B, where B is the
26dB emission bandwidth in MHz. This is slightly more than 23 dBm for
20 MHz channels.
This patch updates both. Also add links to the two documents into the
database.
[1] http://www.motc.gov.tw/websitedowndoc?file=post/201411171137330.doc&filedisplay=Table+of+radio+frequency+allocation.doc
[2] http://www.ncc.gov.tw/english/show_file.aspx?table_name=news&file_sn=681
Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The Radio Frequency Spectrum Regulations 2015 [1] drops the
requirement for DFS and TPC in the 5490-5710 MHz range. Update
the database to remove DFS for this range and remove the 3dB drop
in the transmit power limit for TPC.
[1] http://www.ellipsis.co.za/wp-content/uploads/2014/12/Radio-Frequency-Spectrum-Regulations-2015.pdf
Cc: Karl Möller <karl@excors.net>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Based on [1], Hong Kong follows ETSI requirements for DFS.
[1] http://www.ofca.gov.hk/filemanager/ofca/en/content_401/hkta1039.pdf
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Related regulation:
http://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf10971.html#s6.2.3
Frequency Bands 5470-5600 MHz and 5650-5725 MHz
Until further notice, devices subject to this section [i.e. Wifi device
supporting 5 GHz bands] shall not be capable of transmitting in the band
5600-5650 MHz. This restriction is for the protection of Environment
Canada’s weather radars operating in this band.
Signed-off-by: Wei Zhong <wzhong@google.com>
[ saf: Adjusted 5490-5590 MHz range up to 5600 MHz ]
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Source is document named
Changes to NLA 124_Order №129_22042015.pdf
Signed-off-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Source is ARIB STD-T74, available at:
http://www.arib.or.jp/english/html/overview/doc/1-STD-T74v1_1.pdf
Signed-off-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The ETSI EN 300 440-1 and EN 300 440-2 standards mandate the use of the
5725mHz - 5875mHz band as follows:
Application - Generic use
Maximum Radiated Power - 25mW
The Bulgarian Communications Regulations Commission has made the
decision to harmonise its regulations for this band with the EU
regulations [1], [2].
Based on this data, introduce the 5725mHz - 5875mHz band for the BG
regulatory domain.
[1] http://crc.bg/files/_bg/Spisak_2015.pdf
[2] http://crc.bg/files/_bg/Pravila_2015_resh24.pdf
Signed-off-by: Petko Bordjukov <bordjukov@gmail.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Change DFS domain to DFS-ETSI for Australia and New Zealand
Source: AS/NZS 4268 (not avilable online).
Signed-off-by: Dmitry Ivanov <dima@ubnt.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Source:
http://www.cam.gov.mv/docs/tech_standards/TAM-TS-100-2004-WLAN.pdf
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
source: http://www.dsrt.gov.mo/por/laws/198_2014.html
on July 30, 2014
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The FCC approved UNII devices operating in
the 5600 - 5650MHz (TDWR) range with radar
detection and DFS capabilities.
Effective 6/2/2014.
Signed-off-by: Guy Mishol <guym@ti.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
VHT80 was incorrectly enabled for number of countries.
40 and 80 MHz channels are not allowed on 5 GHz for these:
- Armenia (AM)
- Bahrain (BH)
- Costa Rica (CR)
- Ecuador (EC)
- Guam (GU)
- Indonesia (ID) (also remove 40 MHz from 2.4 GHz)
- North Korea (KP)
- Sri Lanka (LK)
- El Salvador (SV)
80 MHz channels are not allowed on 5 GHz for these:
- Egypt (EG)
- Russia (RU)
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
The FCC approved UNII devices operating in the
5470 - 5725MHz range with radar detection and DFS
capabilities. See the [1] source for details.
[1] https://apps.fcc.gov/oetcf/kdb/forms/FTSSearchResultPage.cfm?id=41732&switch=P
Signed-off-by: Daiwei Li <daiweili@suitabletech.com>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
|
|
As announced by John [1], I'm taking over maintaintership of the
wireless regulatory databse. Make it official by adding my key,
removing John's, and updating the Makefile and documentation to
reflect the change in maintainer.
[1] http://permalink.gmane.org/gmane.linux.kernel.wireless.general/131573
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
This makes it easier to write (semi-)automated synchronization and
validation scripts against external databases. I'd assume this order was
already supposed to be used, but couple of the countries have been
placed in incorrect locations in the file over the years.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
Comply to final document: Etsi En 302 567
Signed-off-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Acked-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
This extends regulatory rules for Venezuela to allow 160 MHz VHT channels
to be used in 5.15-5.25 GHz, 5.25-5.35 GHz. Since the rules between
5.15-5.25 and 5.25-5.35 GHz ranges are different (e.g., DFS
requirement), the AUTO-BW flag needs to be used to allow the maximum
channel bandwidth to be determined automatically based on two rules.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
This extends regulatory rules for Panama to allow 160 MHz VHT channels
to be used in 5.15-5.25 GHz, 5.25-5.35 GHz. Since the rules between
5.15-5.25 and 5.25-5.35 GHz ranges are different (e.g., DFS
requirement), the AUTO-BW flag needs to be used to allow the maximum
channel bandwidth to be determined automatically based on two rules.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
This extends regulatory rules for Malaysia to allow 160 MHz VHT channels
to be used in 5.15-5.25 GHz, 5.25-5.35 GHz. Since the rules between
5.15-5.25 and 5.25-5.35 GHz ranges are different (e.g., DFS
requirement), the AUTO-BW flag needs to be used to allow the maximum
channel bandwidth to be determined automatically based on two rules.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
This extends regulatory rules for Algeria to allow 160 MHz VHT channels
to be used in 5.15-5.25 GHz, 5.25-5.35 GHz, and 5.47-5.725 GHz ranges.
Since the rules between 5.15-5.25 and 5.25-5.35 GHz ranges are different
in most cases (e.g., DFS requirement), the AUTO-BW flag needs to be used
to allow the maximum channel bandwidth to be determined automatically
based on two rules. The larger 5.47-5.725 GHz range is large enough to
fit the full 160 MHz channel in a single rule, so that does not require
similar handling and can just change the maximum allowed bandwidth to
160 MHz in the rule.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
This extends regulatory rules for Dominica to allow 160 MHz
VHT channels to be used in 5.15-5.25 GHz, 5.25-5.35 GHz. Since the rules
between 5.15-5.25 and 5.25-5.35 GHz ranges are different (e.g., DFS
requirement), the AUTO-BW flag needs to be used to allow the maximum
channel bandwidth to be determined automatically based on two rules.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
This extends regulatory rules for Dominican Republic to allow 160 MHz
VHT channels to be used in 5.15-5.25 GHz, 5.25-5.35 GHz. Since the rules
between 5.15-5.25 and 5.25-5.35 GHz ranges are different (e.g., DFS
requirement), the AUTO-BW flag needs to be used to allow the maximum
channel bandwidth to be determined automatically based on two rules.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
This extends regulatory rules for Barbados to allow 160 MHz VHT channels
to be used in 5.15-5.25 GHz, 5.25-5.35 GHz. Since the rules between
5.15-5.25 and 5.25-5.35 GHz ranges are different (e.g., DFS
requirement), the AUTO-BW flag needs to be used to allow the maximum
channel bandwidth to be determined automatically based on two rules.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
|
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
