enum wiphy_flags — wiphy capability flags
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_ENFORCE_COMBINATIONS
};
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).
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.
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
if not set, do not allow changing the netns of this wiphy at all
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
supports 4addr mode even on AP (with a single station on a VLAN interface)
supports 4addr mode even as a station
This device supports setting the control port protocol ethertype. The device also honours the control_port_no_encrypt flag.
The device supports IBSS RSN.
The device supports mesh authentication by routing
auth frames to userspace. See NL80211_MESH_SETUP_USERSPACE_AUTH.
The device supports scheduled scans.
Set this flag to enforce interface combinations for this device. This flag is used for backward compatibility only until all drivers advertise combinations and they will always be enforced.