#527: document wext compliance
-----------------------------------------+----------------------------------
      Reporter:  kelmo                   |       Owner:  kelmo                  
             
          Type:  task                    |      Status:  assigned               
             
      Priority:  trivial                 |   Milestone:  version 1.0.0 - first 
stable release
     Component:  madwifi: documentation  |     Version:  trunk                  
             
    Resolution:                          |    Keywords:                         
             
Patch_attached:  0                       |  
-----------------------------------------+----------------------------------
Comment (by [EMAIL PROTECTED]):

 Having just spent the past 2 days looking at MADWiFi's Wireless Extensions
 support, I thought I'd chime in.

 As of snapshot r1648, MADWiFi partially supports WE version 18:

  * no support for '''SIOCSIWPMKSA''' ( WPA2 PMKSA cache operation ); ioctl
 code not present.
  * only new wireless event used is '''IWEVGENIE''' ( generic IE element );
 used in lieu of '''WIEVCUSTOM''' RSN/WPA IE elements.
  * new '''SIOCSIWSCAN''' request params (used for controlling scanning
 behavior) not used.
  * '''SIOCSIWAUTH''' - the following parameters are not supported and
 return the {{{errno}}} '''EOPNOTSUPP''' ( see ticket #566 for details ):
    * '''IW_AUTH_80211_AUTH_ALG''' - sets the authentication algorithm (
 Open | Shared | LEAP ).
    * '''IW_AUTH_RX_UNENCRYPTED_EAPOL''' - allows uncrypted EAPOL messages
 if pairwise keys are set and WPA is ''not'' enabled.
  * '''SIOCGIWRANGE''' - returns ''13'' for {{{we_version_source}}} instead
 of ''18'' ( '''Note''' - I think {{{we_version_source}}} is supposed to
 return the version of Wireless Extensions supported by the driver itself,
 whereas {{{we_version_compiled}}} is the version supported by the kernel
 ).

 I've also found that after patching my kernel (2.6.12) with the WE18 patch
 and rebuilding MADWiFi 0.9.0, wpa_supplicant (0.4.7) won't associate with
 any access points ( I've tried WPA-PSK and WEP ) if I start it with
 ''-Dwext''.  It works just fine if I start it with ''-Dmadwifi''.  I
 haven't debugged the problem yet.

-- 
Ticket URL: <http://madwifi.org/ticket/527>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets

Reply via email to