freq_reg_info(9) [centos man page]

FREQ_REG_INFO(9)					  Regulatory enforcement infrast					  FREQ_REG_INFO(9)

NAME

       freq_reg_info - get regulatory information for the given frequency

SYNOPSIS

       const struct ieee80211_reg_rule * freq_reg_info(struct wiphy * wiphy, u32 center_freq);

ARGUMENTS

       wiphy
	   the wiphy for which we want to process this rule for

       center_freq
	   Frequency in KHz for which we want regulatory information for

DESCRIPTION

       Use this function to get the regulatory rule for a specific frequency on a given wireless device. If the device has a specific regulatory
       domain it wants to follow we respect that unless a country IE has been received and processed already.

RETURN

       A valid pointer, or, when an error occurs, for example if no rule can be found, the return value is encoded using ERR_PTR. Use IS_ERR to
       check and PTR_ERR to obtain the numeric return value. The numeric return value will be -ERANGE if we determine the given center_freq does
       not even have a regulatory rule for a frequency range in the center_freq's band. See freq_in_rule_band for our current definition of a band
       -- this is purely subjective and right now it's 802.11 specific.

AUTHOR

       Johannes Berg <johannes@sipsolutions.net>
	   Author.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							  FREQ_REG_INFO(9)

CRDA(8) 							       Linux								   CRDA(8)

NAME

       crda - send to the kernel a wireless regulatory domain for a given ISO / IEC 3166 alpha2

SYNOPSIS

       crda

Description
       crda is the Linux wireless central regulatory domain agent.  crda is intended to be used by udev scripts and should not be run manually
       unless debugging udev scripts.  crda is triggered to run by the kernel by sending a udev event upon a new regulatory domain change. Regula-
       tory domain changes are triggered by the wireless kernel subsystem (upon initialization and on reception of country IEs), wireless drivers,
       or userspace (see iw ). Upon a regulatory domain change the kernel sends a udev change event for the regulatory platform. The kernel
       ignores regulatory domains sent to it if it does not expect them. The regulatory domain is read by crda from the regulatory.bin file.

RSA Digital Signature
       If built with openssl or gcrypt support crda will have embedded into it an RSA digital signature which will prevent it from reading cor-
       rupted or non-authored regulatory.bin files. Authorship is respected by the RSA public key packed into crda.  This specific crda package
       has been built with an RSA public key from John Linville (the Linux wireless kernel maintainer) and as such will only read regulatory.bin
       files signed by him. For further information see the regulatory.bin man page.

UDEV RULE

       A udev regulatory rule must be put in place in order to receive and parse udev events from the kernel in order to get udev to call crda
       with the passed ISO / IEC 3166 alpha2 country code.  An example udev rule which can be used (usually in /lib/udev/rules.d/85-regula-
       tory.rules ):

       KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/sbin/crda"

Environment variable
       Set the COUNTRY environment variable with a specific ISO / IEC 3166 alpha2 country code and then run crda without arguments. This will send
       a regulatory domain for that alpha2 to the kernel.

SEE ALSO

       iw(8) regulatory.bin(5)

       http://wireless.kernel.org/en/developers/Regulatory/

crda								  23 January 2009							   CRDA(8)