From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 3 10:07:43 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 C44FF96A; Thu, 3 Apr 2014 10:07:43 +0000 (UTC) Received: from mx1.pertho.net (87-194-102-137.bethere.co.uk [87.194.102.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "pertho.net", Issuer "pertho.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4EDFD69F; Thu, 3 Apr 2014 10:07:42 +0000 (UTC) Received: from syn.pertho.net (syn.pertho.lan [10.0.29.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: tom) by syn.pertho.net (Postfix) with ESMTPSA id 69B5C1D449F; Thu, 3 Apr 2014 11:02:09 +0100 (BST) Date: Thu, 3 Apr 2014 11:02:07 +0100 From: Tom Murphy To: Adrian Chadd Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 Message-ID: <20140403100207.GA23640@syn.pertho.net> References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <530EEEA5.4090306@shurik.kiev.ua> <20140228230705.GA28290@syn.pertho.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Tom Murphy , freebsd-current , "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: Thu, 03 Apr 2014 10:07:43 -0000 Hi, I'm just wondering if you had any time to look at this? I'm happy to test any patches or diffs. Regards, Tom On Tue, Mar 11, 2014 at 11:03:20AM -0700, Adrian Chadd wrote: > I still don't have any ideas here. I do however want to try hacking > the driver to transmit EAPOL frames at the management rate, and then > ensure the management rate is non-MCS. > > > -a > > > On 28 February 2014 15:14, Adrian Chadd wrote: > > Hi, > > > > the interesting bits: > > > > > > Feb 28 22:55:22 kernel: iwn_tx_data: qid 3 idx 3 len 129 nsegs 2 rate > > 0002 plcp 0x0000420a > > Feb 28 22:55:22 kernel: iwn_tx_data: qid 3 idx 4 len 129 nsegs 2 rate > > 0002 plcp 0x0000420a > > Feb 28 22:55:22 kernel: iwn5000_tx_done: qid 3 idx 3 retries 16 nkill > > 0 rate 80006902 duration 2815 status 83 > > Feb 28 22:55:22 kernel: iwn5000_tx_done: qid 3 idx 4 retries 16 nkill > > 0 rate 80006902 duration 2815 status 83 > > Feb 28 22:55:23 kernel: iwn_tx_data: qid 3 idx 5 len 129 nsegs 2 rate > > 0002 plcp 0x0000420a > > Feb 28 22:55:23 kernel: iwn_tx_data: qid 3 idx 6 len 129 nsegs 2 rate > > 0002 plcp 0x0000420a > > Feb 28 22:55:23 kernel: iwn5000_tx_done: qid 3 idx 5 retries 16 nkill > > 0 rate 80006902 duration 2815 status 83 > > Feb 28 22:55:23 kernel: iwn5000_tx_done: qid 3 idx 6 retries 16 nkill > > 0 rate 80006902 duration 2815 status 83 > > Feb 28 22:55:24 kernel: iwn_tx_data: qid 3 idx 7 len 129 nsegs 2 rate > > 0002 plcp 0x0000420a > > Feb 28 22:55:24 kernel: iwn_tx_data: qid 3 idx 8 len 129 nsegs 2 rate > > 0002 plcp 0x0000420a > > Feb 28 22:55:24 kernel: iwn5000_tx_done: qid 3 idx 7 retries 16 nkill > > 0 rate 80006902 duration 2815 status 83 > > Feb 28 22:55:24 kernel: iwn5000_tx_done: qid 3 idx 8 retries 16 nkill > > 0 rate 80006902 duration 2815 status 83 > > > > .. so it's failing to transmit the management frames after association > > - they're being transmitted at MCS0 and the AP is just plain not > > ACKing them. > > > > Now, I don't know why this is. It's trying to transmit the initial > > frame at non-MCS rates, but I have a feeling the multi-rate retry > > table thing is confusing it and it's trying to send it as MCS. So > > maybe the AP doesn't like management frames at MCS rates. > > > > I'll have to think about this a little. > > > > -a > > > > > > On 28 February 2014 15:07, Tom Murphy wrote: > >> I've attached my iwn debug messages to this email starting > >> with the point I tried to associate to the Wifi. > >> > >> Thanks again for looking at this! > >> > >> Kind regards, > >> Tom > >> > >> On Thu, Feb 27, 2014 at 12:13:51PM -0800, Adrian Chadd wrote: > >>> On 26 February 2014 23:52, Alexandr wrote: > >>> > Tom, could you: > >>> > > >>> > 1. compile kernel WITH_IWNDEBUG > >>> > 2. sysctl dev.iwn.0.debug=0x1 > >>> > 3. wlandebug -i wlan0 auth+assoc > >>> > 4. Associate with AP in 11n mode > >>> > 5. Send us appropriate /var/log/messages > >>> > > >>> > Then I try to compare it with my log. > >>> > >>> Please do. I've been trying to track down the source of this "ht just > >>> doesn't work!" but it works fine with all of the Intel NICs I have > >>> here. > >>> > >>> Can someone see if they can find a mtaching NIC online (amazon,ebay?) > >>> Owning one that I can whack in a laptop is likely going ot help things > >>> a lot. > >>> > >>> Thanks, > >>> > >>> > >>> -a