that first appeared in NetBSD and then FreeBSD. The wlan module may
also force the loading of additional modules for crypto support
(wlan_wep, wlan_tkip, wlan_ccmp, etc.), for MAC-based ACL support
-(wlan_acl), and for 802.1x authenticator support (wlan_auth,
-wlan_radius). The latter modules are only used when operating as an AP.
-The crypto modules are loaded when keys of that type are created.
+(wlan_acl), and for 802.1x authenticator support (wlan_xauth). The
+latter modules are only used when operating as an AP. The crypto
+modules are loaded when keys of that type are created.
The ath_hal module contains the Atheros Hardware Access Layer (HAL).
This code manages much of the chip-specific operation of the driver.
then FreeBSD. The wlan module may also force the loading of
additional modules for crypto support (wlan_wep, wlan_tkip, wlan_ccmp,
etc.), for MAC-based ACL support (wlan_acl), and for 802.1x
-authenticator support (wlan_auth, wlan_radius)). The latter modules
-are only used when operating as an AP. The crypto modules are
-loaded when keys of that type are created.
+authenticator support (wlan_xauth). The latter modules are only
+used when operating as an AP. The crypto modules are loaded when
+keys of that type are created.
%prep
#%setup -q
TOP = $(obj)/..
#
-# There are two authenticator mechanisms: an in-kernel implementation
-# (wlan_auth+wlan_radius) and an external implementation (wlan_xauth) that
-# requires a user process to manage the authentication process. By default
-# the external authenticator is used. ieee80211_proto.c has a table of module
-# names that defines the default module to auto-load for each authentication
-# scheme; to get the in-kernel authenticator by default modify it to load
-# wlan_auth instead of wlan_xauth or manually load wlan_auth prior to use.
-#
+# There is one authenticator mechanism: an in-kernel implementation
+# (wlan_xauth).
+#
MOD_AUTH := wlan_xauth.o
#
# Scanning policy is split into modules. The default policy modules
EXTRA_CFLAGS += $(INCS) $(COPTS) -DOPT_AH_H=\"public/$(TARGET).opt_ah.h\"
#
-# There are two authenticator mechanisms: an in-kernel implementation
-# (wlan_auth+wlan_radius) and an external implementation (wlan_xauth) that
-# requires a user process to manage the authentication process. By default
-# the external authenticator is used. ieee80211_proto.c has a table of module
-# names that defines the default module to auto-load for each authentication
-# scheme; to get the in-kernel authenticator by default modify it to load
-# wlan_auth instead of wlan_xauth or manually load wlan_auth prior to use.
+# There is one authenticator mechanism: an in-kernel implementation
+# (wlan_xauth).
#
MOD_AUTH := wlan_xauth.o
#
const struct ieee80211_authenticator_backend *
ieee80211_authenticator_backend_get(const char *name)
{
- if (backend == NULL)
- ieee80211_load_module("wlan_radius");
return backend && strcmp(backend->iab_name, name) == 0 ? backend : NULL;
}
EXPORT_SYMBOL(ieee80211_authenticator_backend_get);