On Fri, 2014-03-14 at 21:31 -0700, Adrian Chadd wrote:
> What other drivers are missing this?
> 
> 
> Adrian
> 

From my quick search, many of the older ones.

The list is quicker if we talk about the ones that *do* have it:

ath(4)
run(4)
mwl(4)
ndis(4)
wi(4)

It looks like the capabilities struct defines that the driver/hardware
will provide to wpa_supplicant.

Using the pre-2.0 wpa_supplicant seems to work with iwn(4) as well.

sean




> 
> On Mar 14, 2014 7:52 PM, "Sean Bruno" <sbr...@ignoranthack.me> wrote:
>         It looks like the wpa_supplicant 2.0 import now checks the
>         cryptocapability mask when trying to validate WEP usage.
>         
>         iwn(4) does not populate the mask with any values so
>         wpa_supplicant sees
>         a value of 0.
>         
>         I added the capabilites and can associate, but dhclient cannot
>         get an IP
>         from the AP.  I assume then, that once again, I don't know
>         what I'm
>         doing.
>         
>         More or less, this is what I tried:
>         
>         Index: if_iwn.c
>         ===================================================================
>         --- if_iwn.c    (revision 263173)
>         +++ if_iwn.c    (working copy)
>         @@ -564,6 +564,8 @@
>                         | IEEE80211_C_PMGT              /*
>         Station-side power mgmt */
>                         ;
>         
>         +        ic->ic_cryptocaps = IEEE80211_CRYPTO_WEP;
>         +
>                 /* Read MAC address, channels, etc from EEPROM. */
>                 if ((error = iwn_read_eeprom(sc, macaddr)) != 0) {
>                         device_printf(dev, "could not read EEPROM,
>         error %d\n",
>         
>         
>         sean
>         
>         p.s. Allan Jude came up with a hack for wpa_supplicant that
>         seems to
>         work, so I've bcc'd him here to get a patch out of him.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to