Date: Fri, 14 Mar 2014 21:31:50 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Sean Bruno <sbruno@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: iwn(4) and WEP Message-ID: <CAJ-Vmo=GiEY1hJm27DVWi7ka3hfySHsMRmLc7F_d=Gey_AChjg@mail.gmail.com> In-Reply-To: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> References: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
What other drivers are missing this?
Adrian
On Mar 14, 2014 7:52 PM, "Sean Bruno" <sbruno@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.
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=GiEY1hJm27DVWi7ka3hfySHsMRmLc7F_d=Gey_AChjg>