From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 04:43:10 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 66DE2F50; Sat, 15 Mar 2014 04:43:10 +0000 (UTC) Received: from mail.ignoranthack.me (ujvl.x.rootbsd.net [199.102.79.106]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 43A84BB1; Sat, 15 Mar 2014 04:43:09 +0000 (UTC) Received: from [192.168.11.100] (unknown [180.42.49.96]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id E2E08192ACD; Sat, 15 Mar 2014 05:08:58 +0000 (UTC) Subject: Re: iwn(4) and WEP From: Sean Bruno To: Adrian Chadd In-Reply-To: References: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-cfC5AGKMLFrKqfq+QaMX" Date: Sat, 15 Mar 2014 13:43:01 +0900 Message-ID: <1394858581.2454.4.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: sbruno@freebsd.org List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Mar 2014 04:43:10 -0000 --=-cfC5AGKMLFrKqfq+QaMX Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Fri, 2014-03-14 at 21:31 -0700, Adrian Chadd wrote: > What other drivers are missing this? >=20 >=20 > Adrian >=20 =46rom 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 >=20 > On Mar 14, 2014 7:52 PM, "Sean Bruno" wrote: > It looks like the wpa_supplicant 2.0 import now checks the > cryptocapability mask when trying to validate WEP usage. > =20 > iwn(4) does not populate the mask with any values so > wpa_supplicant sees > a value of 0. > =20 > 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. > =20 > More or less, this is what I tried: > =20 > 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 */ > ; > =20 > + 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", > =20 > =20 > sean > =20 > 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. --=-cfC5AGKMLFrKqfq+QaMX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAABAgAGBQJTI9pRAAoJEBkJRdwI6BaHJM4IAIehOWj0XtZDtrtT3A0s4Hr3 uFFdr7xyEYc5bBgbu7GHaR4eH+S4LUqP7KTXu/7Kya26V+0cxaLFQ1ewzp727wDj ful48NvLa2ZWs+3xhl6ClNadGAzB3jzF/qFnveJKxvWPNJzOQnsnrv6iLJumVn8J MiWpFpOg3rGAP0ts79twthNh2oGiMEsO6yGV/vnGRfU7rUwN9KIt5er7kfOfo6aO +xiq2OjO33fQtQZ9BCmfqsG3l4x+4BrY2djSBOE037OZpQ9+P9H1gm5jvQJedAa7 Hv9dDJB53bM8Ch5XW/T5yFA5IT8IDeG7xloyAJX908UMq0Cx0RLMflKTax2bFs4= =ftmC -----END PGP SIGNATURE----- --=-cfC5AGKMLFrKqfq+QaMX--