NOTE: this page is for archival only, see the note at the end of the page.

Central Regulatory Domain Agent

CRDA acts as the udev helper for communication between the kernel and userspace for regulatory compliance. It relies on nl80211 for communication. CRDA is intended to be run only through udev communication from the kernel. The user should never have to run it manually except if debugging udev issues.

License

CRDA is licensed under the ISC license in hopes other operating systems can benefit from a community project to enhance regulatory considerations.

Code

You can get the latest CRDA code from:

git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/crda.git

Releases

You can get CRDA releases here

Host requirements

  • libc/ublibc
  • regulatory.bin file
  • libnl >= libnl1

Build requirements

  • python and the m2crypto package (python-m2crypto)
  • libgcrypt or libssl (openssl) header files
  • nl library and header files (libnl1 and libnl-dev) available at git://git.kernel.org/pub/scm/libs/netlink/libnl.git
  • RSA public key of John Linville, we include this as part of this package so you do not need to install it. This RSA public key comes from the wireless-regdb.git tree and we keep it up to date here.
  • regulatory database (regulatory.bin, no need to build just put the file in REG_BIN location) from:

   git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-regdb.git

Letting the kernel call CRDA

We use userspace events (uevents) to let the kernel speak to userspace. Below is an example udev rule you can place into your distribution's udev rules directory (usually /etc/udev/rules.d/). Note that most distributions have udev configured with inotify on the udev rules directory, so there is no need to restart udev after adding the new rule.

# Example file, should be put in /etc/udev/rules.d/regulatory.rules
KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/sbin/crda"

Changing regulatory domains

Userspace applications can request the kernel to change regulatory domains. The following userspace applications currently allow you to do this:

Using iw to change regulatory domains

You can use iw from the command line as follows:

iw reg set US

Using wpa_supplicant to change regulatory domains

Get the wpa_supplicant (as of 0.6.7) and then add as part of your configuration file a line that has something like this:

COUNTRY=US

Using Network Manager to change regulatory domains

This needs to be implemented, but since Network Manager uses wpa_supplicant it should just be a matter of adding a user interface option to let a user select an alpha2 and then adding the country entry into the wpa_supplicant configuration entered.

Debugging kernel to CRDA communication

To debug communication between the kernel and udev you can monitor udev events:

udevadm monitor --environment kernel

This is a static dump of the wiki, taken after locking it in January 2015. The new wiki is at https://wireless.wiki.kernel.org/.
versions of this page: last, v53, v52, v51, v50, v49, v48, v47, v46, v45, v44, v43, v42, v41, v40, v39, v38, v37, v36, v35, v34, v33, v32, v31, v30, v29, v28, v27, v26, v25, v24, v23, v22, v21, v20, v19, v18, v17, v16, v15, v14, v13, v12, v11, v10, v9, v8, v7, v6, v5, v4, v3, v2, v1