| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|