ieee80211_alloc_countryie(9) [debian man page]
IEEE80211_REGDOMAIN(9) BSD Kernel Developer's Manual IEEE80211_REGDOMAIN(9) NAME
ieee80211_regdomain -- 802.11 regulatory support SYNOPSIS
#include <net80211/ieee80211_var.h> #include <net80211/ieee80211_regdomain.h> int ieee80211_init_channels(struct ieee80211com *, const struct ieee80211_regdomain *, const uint8_t bands[]); void ieee80211_sort_channels(struct ieee80211_channel *, int nchans); struct ieee80211_appie * ieee80211_alloc_countryie(struct ieee80211com *); DESCRIPTION
The net80211 software layer provides a support framework for drivers that includes comprehensive regulatory support. net80211 provides mech- anisms that enforce regulatory policy by privileged user applications. Drivers define a device's capabilities and can intercept and control regulatory changes requested through net80211. The initial regulatory state, including the channel list, must be filled in by the driver before calling ieee80211_ifattach(). The channel list should reflect the set of channels the device is calibrated for use on. This list may also be requested later through the ic_getradiocaps method in the ieee80211com structure. The ieee80211_init_channels() function is provided as a rudimentary fallback for drivers that do not (or cannot) fill in a proper channel list. Default regulatory state is supplied such as the regulatory SKU, ISO country code, location (e.g. indoor, outdoor), and a set of frequency bands the device is capable of operating on. net80211 populates the channel table in ic_channels with a default set of channels and capabilities. Note this mechanism should be used with care as any mismatch between the channel list created and the device's capabilities can result in runtime errors (e.g. a request to operate on a channel the device does not support). The SKU and country information are used for generating 802.11h protocol elements and related operation such as for 802.11d; mis-setup by a driver is not fatal, only potentially confusing. Devices that do not have a fixed/default regulatory state can set the regulatory SKU to SKU_DEBUG and country code to CTRY_DEFAULT and leave proper setup to user applications. If default settings are known they can be installed and/or an event can be dispatched to user space using ieee80211_notify_country() so that devd(8) will do the appropriate setup work at system boot (or device insertion). The channel table is sorted to optimize lookups using the ieee80211_sort_channels() routine. This should be done whenever the channel table contents are modified. The ieee80211_alloc_countryie() function allocates an information element as specified by 802.11h. Because this is expensive to generate it is cached in ic_countryie and generated only when regulatory state changes. Drivers that call ieee80211_alloc_countryie() directly should not help with this caching; doing so may confuse the net80211 layer. DRIVER REGULATORY CONTROL
Drivers can control regulatory change requests by overriding the ic_setregdomain method that checks change requests. While drivers can reject any request that does not meet its requirements it is recommended that one be lenient in what is accepted and, whenever possible, instead of rejecting a request, alter it to be correct. For example, if the transmit power cap for a channel is too high the driver can either reject the request or (better) reduce the cap to be compliant. Requests that include unacceptable channels should cause the request to be rejected as otherwise a mismatch may be created between application state and the state managed by net80211. The exact rules by which to operate are still being codified. SEE ALSO
regdomain(5), ifconfig(8), ieee80211(9) BSD
August 4, 2009 BSD
Check Out this Related Man Page
ENUM
WIPHY_FLAGS(9) Device registration ENUM WIPHY_FLAGS(9) NAME
enum_wiphy_flags - wiphy capability flags SYNOPSIS
enum wiphy_flags { WIPHY_FLAG_CUSTOM_REGULATORY, WIPHY_FLAG_STRICT_REGULATORY, WIPHY_FLAG_DISABLE_BEACON_HINTS, WIPHY_FLAG_NETNS_OK, WIPHY_FLAG_PS_ON_BY_DEFAULT, WIPHY_FLAG_4ADDR_AP, WIPHY_FLAG_4ADDR_STATION, WIPHY_FLAG_CONTROL_PORT_PROTOCOL, WIPHY_FLAG_IBSS_RSN, WIPHY_FLAG_MESH_AUTH, WIPHY_FLAG_SUPPORTS_SCHED_SCAN, WIPHY_FLAG_SUPPORTS_FW_ROAM, WIPHY_FLAG_AP_UAPSD, WIPHY_FLAG_SUPPORTS_TDLS, WIPHY_FLAG_TDLS_EXTERNAL_SETUP, WIPHY_FLAG_HAVE_AP_SME, WIPHY_FLAG_REPORTS_OBSS, WIPHY_FLAG_AP_PROBE_RESP_OFFLOAD, WIPHY_FLAG_OFFCHAN_TX, WIPHY_FLAG_HAS_REMAIN_ON_CHANNEL }; CONSTANTS
WIPHY_FLAG_CUSTOM_REGULATORY tells us the driver for this device has its own custom regulatory domain and cannot identify the ISO / IEC 3166 alpha2 it belongs to. When this is enabled we will disregard the first regulatory hint (when the initiator is REGDOM_SET_BY_CORE). WIPHY_FLAG_STRICT_REGULATORY tells us the driver for this device will ignore regulatory domain settings until it gets its own regulatory domain via its regulatory_hint unless the regulatory hint is from a country IE. After its gets its own regulatory domain it will only allow further regulatory domain settings to further enhance compliance. For example if channel 13 and 14 are disabled by this regulatory domain no user regulatory domain can enable these channels at a later time. This can be used for devices which do not have calibration information guaranteed for frequencies or settings outside of its regulatory domain. If used in combination with WIPHY_FLAG_CUSTOM_REGULATORY the inspected country IE power settings will be followed. WIPHY_FLAG_DISABLE_BEACON_HINTS enable this if your driver needs to ensure that passive scan flags and beaconing flags may not be lifted by cfg80211 due to regulatory beacon hints. For more information on beacon hints read the documenation for regulatory_hint_found_beacon WIPHY_FLAG_NETNS_OK if not set, do not allow changing the netns of this wiphy at all WIPHY_FLAG_PS_ON_BY_DEFAULT if set to true, powersave will be enabled by default -- this flag will be set depending on the kernel's default on wiphy_new, but can be changed by the driver if it has a good reason to override the default WIPHY_FLAG_4ADDR_AP supports 4addr mode even on AP (with a single station on a VLAN interface) WIPHY_FLAG_4ADDR_STATION supports 4addr mode even as a station WIPHY_FLAG_CONTROL_PORT_PROTOCOL This device supports setting the control port protocol ethertype. The device also honours the control_port_no_encrypt flag. WIPHY_FLAG_IBSS_RSN The device supports IBSS RSN. WIPHY_FLAG_MESH_AUTH The device supports mesh authentication by routing auth frames to userspace. See NL80211_MESH_SETUP_USERSPACE_AUTH. WIPHY_FLAG_SUPPORTS_SCHED_SCAN The device supports scheduled scans. WIPHY_FLAG_SUPPORTS_FW_ROAM The device supports roaming feature in the firmware. WIPHY_FLAG_AP_UAPSD The device supports uapsd on AP. WIPHY_FLAG_SUPPORTS_TDLS The device supports TDLS (802.11z) operation. WIPHY_FLAG_TDLS_EXTERNAL_SETUP The device does not handle TDLS (802.11z) link setup/discovery operations internally. Setup, discovery and teardown packets should be sent through the NL80211_CMD_TDLS_MGMT command. When this flag is not set, NL80211_CMD_TDLS_OPER should be used for asking the driver/firmware to perform a TDLS operation. WIPHY_FLAG_HAVE_AP_SME device integrates AP SME WIPHY_FLAG_REPORTS_OBSS the device will report beacons from other BSSes when there are virtual interfaces in AP mode by calling cfg80211_report_obss_beacon. WIPHY_FLAG_AP_PROBE_RESP_OFFLOAD When operating as an AP, the device responds to probe-requests in hardware. WIPHY_FLAG_OFFCHAN_TX Device supports direct off-channel TX. WIPHY_FLAG_HAS_REMAIN_ON_CHANNEL Device supports remain-on-channel call. AUTHOR
Johannes Berg <johannes@sipsolutions.net> Author. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 ENUM WIPHY_FLAGS(9)