Return-path: Received: from mail-we0-f182.google.com ([74.125.82.182]:64099 "EHLO mail-we0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756613Ab3KHOGi (ORCPT ); Fri, 8 Nov 2013 09:06:38 -0500 Received: by mail-we0-f182.google.com with SMTP id t61so2048910wes.27 for ; Fri, 08 Nov 2013 06:06:36 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <526E20EA.9090203@rempel-privat.de> From: Krishna Chaitanya Date: Fri, 8 Nov 2013 19:36:16 +0530 Message-ID: (sfid-20131108_150641_762058_E2F292AA) Subject: Re: I always need a miracle to connect with iwlwifi To: Felipe Contreras Cc: Oleksij Rempel , ilw@linux.intel.com, "hostap@lists.shmoo.com" , linux-wireless Mailing List Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, Nov 8, 2013 at 6:44 PM, Felipe Contreras wrote: > On Fri, Nov 8, 2013 at 2:35 AM, Felipe Contreras > wrote: >> On Sat, Nov 2, 2013 at 2:05 PM, Krishna Chaitanya >> wrote: >> >>> Also one more thing you said N900 uses mac80211 and it has no issues, but as >>> its a embedded device it might running an older kernel where the >>> handling might be >>> different, so we need to try with the same kernel you are facing an >>> issue with the >>> a driver which advertises IEEE80211_HW_NEED_DTIM_BEFORE_ASSOC. >> >> Yes it was running an older kernel, but I just compiled v3.12 and ran >> it on the N900, and still everything works fine. >> >>> (or) if you a have a compilation environment try commenting the advertisement of >>> IEEE80211_HW_NEED_DTIM_BEFORE_ASSOC in the iwlwifi DVM driver and >>> try to reproduce the issue. >> >> After commenting that flag everything works fine :) Oh, great. That was just to corner the problem, that means we are not getting the required beacon before the association, but we only wait for 1 beacon here may be we to wait for some number of beacons before giving up the association?? Johannes?? >> What are the next steps? > > I tried to add some debugging to see what's going on, and indeed the > beacon packets are lost, I added debugging as low in the chain as I > could (iwlagn_rx_reply_rx()), and I don't see them there. However, > when I enable the monitor mode, I see them. What's going on? In the captures you shared all the beacons are malformed, so probably they failed the CRC check. iwlwifi drops all the CRC failed packets. (doth MVM and DVM) Not sure how you are receiving the beacons in the monitor mode. BTW did you tried capturing the beacons in other devices and see if they are really malformed, or is it just iwlwifi interpreting them wrongly.?