From owner-freebsd-current@FreeBSD.ORG Tue Mar 11 18:03:22 2014 Return-Path: Delivered-To: freebsd-current@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 1B0BA89A; Tue, 11 Mar 2014 18:03:22 +0000 (UTC) Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B7372789; Tue, 11 Mar 2014 18:03:21 +0000 (UTC) Received: by mail-qg0-f43.google.com with SMTP id f51so9716536qge.2 for ; Tue, 11 Mar 2014 11:03:21 -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=i4+XfluFzo/cAwSVfvf/cMrxRv8j/gmhoi6SqtKHL74=; b=GZBKTrKHflKuanah+F6lP5T7R3Df3jyTdvbcgeW/932PtyTQqfvoOksbGOjPb//sQM TmO6F5Bk9atWYNHH9ooRgDbzNpXnSzKEbJaJ/Ze9FybgTV4Q9joZ00CN9Vobphm1rju3 mGqwwAgs+pKcSKYgudmLwGLuUYP58uuhaOpWzjzAiaa35td7/5QNapQovUlE0kaRi3+t l0ez2kr25ZdXwKq2EZI7j/tMweDOFgWiDOQqZR94pvXtBvkvxMpWvvYAmmzTXo+Y/ZW1 OVAdsFIuWA/pXZaLMPS9jd+hAPjEmsZ/qskd6X/jgHxCE8t4QlRuP5J+BHaoQfLPv/sj +BTw== MIME-Version: 1.0 X-Received: by 10.224.13.142 with SMTP id c14mr4803647qaa.76.1394561000942; Tue, 11 Mar 2014 11:03:20 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.8.137 with HTTP; Tue, 11 Mar 2014 11:03:20 -0700 (PDT) In-Reply-To: References: <20140226123709.GA31099@syn.pertho.net> <530EE7F4.3080903@shurik.kiev.ua> <530EEEA5.4090306@shurik.kiev.ua> <20140228230705.GA28290@syn.pertho.net> Date: Tue, 11 Mar 2014 11:03:20 -0700 X-Google-Sender-Auth: h0wlVnLcz7Wn7hfZsadDYtyx9kA Message-ID: Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 From: Adrian Chadd To: Tom Murphy Content-Type: text/plain; charset=ISO-8859-1 Cc: Alexandr , freebsd-current , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Mar 2014 18:03:22 -0000 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