#462: Current WEXT Standard Compliance
---------------------------------------------------+------------------------
Reporter: Eli Crifield <[EMAIL PROTECTED]> | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: 802.11 stack | Version:
Keywords: | Patch_attached: 0
---------------------------------------------------+------------------------
From Dan Williams:
http://mail.gnome.org/archives/networkmanager-list/2006-
March/msg00159.html
Madwifi probably supports these basic bits already; they include, for
example, SIOCGIWENCODE, SIOCSIWENCODE, pretty much _any_ ioctl that
starts with SIOC[S|G]IW is a WEXT one.
So where madwifi has fallen behind a bit is in the enhancements that
WEXT has made in the past year or so, in both the WEXT-18 and WEXT-19
versions of the interface. First, WPA support has been added and
implemented by a few drivers, and other bits have been solidified. The
bits missing are likely the WPA bits where madwifi has it's own private
ioctls. It used to be that every driver had it's own method for setting
WPA parameters; but in the past year that has been standardised into
WEXT, and drivers now provide a WEXT-standard method for WPA.
Jean Tourrilhes <[EMAIL PROTECTED]> is The Guy for Linux WEXT.
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html
/usr/include/wireless.h
wireless-tools package
The reference implementation of WPA support for WEXT are the Intel
Pro/Wireless and the hostap drivers. These include support for the
following WEXT ioctls:
SIOCGIWAUTH
SIOCSIWAUTH
SIOCGIWENCODEEXT
SIOCSIWENCODEEXT
SIOCGIWGENIE
SIOCSIWGENIE
SIOCSIWPMKSA
SIOCSIWMLME
The other component is supporting wireless events, which are provided by
the kernel using the wireless_send_event() call in driver code. For
example, when the card has finished scanning, it should return a
SIOCGIWSCAN event to user space, when it has associated with an access
point it should return the BSSID of that access point with an SIOCGIWAP
event, etc.
It's fairly easy to port over the support; you just have to map the
options that you get passed from the handlers you register with WEXT to
the internal driver settings. The atmel and airo drivers contain
minimal versions of the IWENCODEEXT and IWAUTH handlers that support
WEP, but it should be pretty clear how to do these from the ipw and
hostap drivers, the kernel 802.11 layer, and the emerging 802.11
"softmac" layer.
Dan
--
Ticket URL: <http://madwifi.org/ticket/462>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
