Date: Sat, 15 Mar 2014 13:49:36 +0900 From: Sean Bruno <sbruno@ignoranthack.me> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: iwn(4) and WEP Message-ID: <1394858976.2454.5.camel@powernoodle.corp.yahoo.com> In-Reply-To: <CAJ-Vmo=z=h_ofOWx_v1OksFAUor=x9bT4EGP2jr%2BfJOaznBakA@mail.gmail.com> References: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> <CAJ-Vmo=GiEY1hJm27DVWi7ka3hfySHsMRmLc7F_d=Gey_AChjg@mail.gmail.com> <1394858581.2454.4.camel@powernoodle.corp.yahoo.com> <CAJ-Vmo=z=h_ofOWx_v1OksFAUor=x9bT4EGP2jr%2BfJOaznBakA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-9O4H1Kb1Y/k746Ri6S3/
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
On Fri, 2014-03-14 at 21:44 -0700, Adrian Chadd wrote:
> Ok. Please file prs for this.
>=20
> I'm glad you all have debugged this!
>=20
>=20
> Adrian
>=20
Well, there's the rub.
Allan's patch works, mine will associate, but passes no traffic. :-)
sean
>=20
> On Mar 14, 2014 9:43 PM, "Sean Bruno" <sbruno@ignoranthack.me> wrote:
> On Fri, 2014-03-14 at 21:31 -0700, Adrian Chadd wrote:
> > What other drivers are missing this?
> >
> >
> > Adrian
> >
> =20
> >From my quick search, many of the older ones.
> =20
> The list is quicker if we talk about the ones that *do* have
> it:
> =20
> ath(4)
> run(4)
> mwl(4)
> ndis(4)
> wi(4)
> =20
> It looks like the capabilities struct defines that the
> driver/hardware
> will provide to wpa_supplicant.
> =20
> Using the pre-2.0 wpa_supplicant seems to work with iwn(4) as
> well.
> =20
> sean
> =20
> =20
> =20
> =20
> >
> > 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
> >
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > --- if_iwn.c (revision 263173)
> > +++ if_iwn.c (working copy)
> > @@ -564,6 +564,8 @@
> > | IEEE80211_C_PMGT /*
> > Station-side power mgmt */
> > ;
> >
> > + ic->ic_cryptocaps =3D IEEE80211_CRYPTO_WEP;
> > +
> > /* Read MAC address, channels, etc from
> EEPROM. */
> > if ((error =3D iwn_read_eeprom(sc, macaddr)) !
> =3D 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.
> =20
--=-9O4H1Kb1Y/k746Ri6S3/
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAABAgAGBQJTI9vgAAoJEBkJRdwI6BaH0eQIAI+tC+zLDEzzpYn75Vyxl9HM
qg32rvC8HbxsCyi9Rhg2m/Y4R7dcAf9TTdBsmPN/1MybUwWCoefx3zxNtcsQ1Fmw
/TdH22uhxsRgQh88JxxZcJEL2eftJtmLjxcKLtZz59X0yorc4sM039y2XnV6DKKT
NeyNlh5Xza2p5M21z86ZdooLn1lcuzoVJgk2dSHrtXAp5Y+zrNjoCX6R13g5lJ5H
0SYOmaiqhvCaIZqMYhg8q/75jQUF9pcIIv1RQOdqpagQOEifFLgDunNUnCdMyRPD
TqIM1ClXf0sBscYngxpnpomin9lkIBrfODaM1ZjXTaAUozlYJep8oMmkCxOqWM8=
=L2Kq
-----END PGP SIGNATURE-----
--=-9O4H1Kb1Y/k746Ri6S3/--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1394858976.2454.5.camel>