From owner-freebsd-wireless@FreeBSD.ORG Sat Mar 15 04:44:58 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9CF13FA7; Sat, 15 Mar 2014 04:44:58 +0000 (UTC) Received: from mail-qg0-x229.google.com (mail-qg0-x229.google.com [IPv6:2607:f8b0:400d:c04::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 47727BC1; Sat, 15 Mar 2014 04:44:58 +0000 (UTC) Received: by mail-qg0-f41.google.com with SMTP id i50so10013993qgf.0 for ; Fri, 14 Mar 2014 21:44:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=bKNMIZC3ruiUmcXf+ZEi9Wyc85qnAT6OzvGJoEOY1j0=; b=sOONlL7whaJ8mbPKgqjJAu6jzVt0q5AL+vGSGXZEcH6IR6amXEcKgsDJn7D3v4PbqO LQNNNUqn/S21Ayqc/rLhM1Se9QnmaAFXohPqq6dKxyQKf3cXWCtWk2di4snl6QehrCKO fy4Lh9Cvh4uroNEvZ3DRMa8I9dS2Cpy8STAZ4A1ZU3GTNAW83ADld22AJid0LK/RoU0A SJIsjcVBEHuxLNY9f92UStjWoQPpFMYgoHBMoO2cjj5nRBRJgcdn1izQLGgPCxMamNZ6 M19GwlX9L9wRKmhH8RIlSNVivKKfRvZS9MiLV89hoJJTtkbrpBU7+Uyts9lXGhM8BGKO NcfQ== MIME-Version: 1.0 X-Received: by 10.224.11.10 with SMTP id r10mr8188071qar.8.1394858696458; Fri, 14 Mar 2014 21:44:56 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.8.137 with HTTP; Fri, 14 Mar 2014 21:44:56 -0700 (PDT) Received: by 10.224.8.137 with HTTP; Fri, 14 Mar 2014 21:44:56 -0700 (PDT) In-Reply-To: <1394858581.2454.4.camel@powernoodle.corp.yahoo.com> References: <1394851922.4791.7.camel@powernoodle.corp.yahoo.com> <1394858581.2454.4.camel@powernoodle.corp.yahoo.com> Date: Fri, 14 Mar 2014 21:44:56 -0700 X-Google-Sender-Auth: aGwUjeloGDHEv--S5UJTAk2xcD4 Message-ID: Subject: Re: iwn(4) and WEP From: Adrian Chadd To: Sean Bruno Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list 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:44:58 -0000 Ok. Please file prs for this. I'm glad you all have debugged this! Adrian On Mar 14, 2014 9:43 PM, "Sean Bruno" wrote: > 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" 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. > >