wext
Subsystems (2)
PATCH 1/1 wext
This patch (wext-patch) is a proposal. It adds two new defines for the SIOCSIWMLME to cover all kinds MLMEs (well, except REASSOC) through a ioctl. (it would be nice to have them, so that I can post the hostapd code for the prism54 card!)
I didn't update the changelog! but this should be done in a matter of seconds.
diffstat wext-patch
wireless.h | 2 ++
1 file changed, 2 insertions(+)
Regards,
Chr. Lamparter
include/linux/wireless.h +2 -0
@@ -546,6 +546,8 @@/* MLME requests (SIOCSIWMLME / struct iw_mlme) */ #define IW_MLME_DEAUTH 0#define IW_MLME_DISASSOC 1 +#define IW_MLME_AUTH 2 +#define IW_MLME_ASSOC 3/* SIOCSIWAUTH/SIOCGIWAUTH struct iw_param flags */ #define IW_AUTH_INDEX 0x0FFF
Quoted 4 lines · On Mon, 2006-10-02 at 19:55 +0200, [email protected] wrote:
This patch (wext-patch) is a proposal. It adds two new defines for the SIOCSIWMLME to cover all kinds MLMEs (well, except REASSOC) through a ioctl. (it would be nice to have them, so that I can post the hostapd code for the prism54 card!)
NACK from me. Please help me work on nl80211 instead :)
johannes
Quoted 9 lines · Johannes Berg
Quoted 4 lines · On Mon, 2006-10-02 at 19:55 +0200, [email protected] wrote:
This patch (wext-patch) is a proposal. It adds two new defines for the SIOCSIWMLME to cover all kinds MLMEs (well, except REASSOC) through a ioctl. (it would be nice to have them, so that I can post the hostapd code for the prism54 card!)
NACK from me. Please help me work on nl80211 instead :)
johannes
hmm... another month of fun. ;)
no really, the problem is that "my" hardware (aka: prism54 fullmac) does all the mac-management, encryption/decryption, AP-Management,... in the firmware. And all "management" operation are wrapped into a simple unique 4-byte "Operation ID"... That's why the WEXT "would be better" for that thing...
(Or, do I mix everything up and nl80211 has "nothing" to do with devicescape's networkstack d80211?)
Chr
Quoted 8 lines · On Wed, 2006-10-04 at 12:56 +0200, [email protected] wrote:
no really, the problem is that "my" hardware (aka: prism54 fullmac) does all the mac-management, encryption/decryption, AP-Management,... in the firmware. And all "management" operation are wrapped into a simple unique 4-byte "Operation ID"... That's why the WEXT "would be better" for that thing...
(Or, do I mix everything up and nl80211 has "nothing" to do with devicescape's networkstack d80211?)
Yes, nl80211 is not tied to d80211, it simply provides a new way of doing configuration.
johannes
Quoted 7 lines · Johannes Berg
Quoted 4 lines · On Mon, 2006-10-02 at 19:55 +0200, [email protected] wrote:
This patch (wext-patch) is a proposal. It adds two new defines for the SIOCSIWMLME to cover all kinds MLMEs (well, except REASSOC) through a ioctl. (it would be nice to have them, so that I can post the hostapd code for the prism54 card!)
NACK from me. Please help me work on nl80211 instead :)
SIOCSIWMLME was designed to allow additional MLME commands to be added. IMHO, a potential replacement in the future should not prevent us from extending WEXT at this point and stop all changes in something that is currently available.
Signature · 1 line
Jouni Malinen PGP id EFC895FA
Quoted 4 lines · Jouni Malinen
SIOCSIWMLME was designed to allow additional MLME commands to be added. IMHO, a potential replacement in the future should not prevent us from extending WEXT at this point and stop all changes in something that is currently available.
Fine with me, it's really just a matter of switch()ing on the sub-command in the cfg80211-we compat code. My answer was more political in nature I guess -- even I need sleep, you know. :P
johannes