Return-path: Received: from mail-wi0-f177.google.com ([209.85.212.177]:41667 "EHLO mail-wi0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751096Ab3KBTNg (ORCPT ); Sat, 2 Nov 2013 15:13:36 -0400 Received: by mail-wi0-f177.google.com with SMTP id f4so2301428wiw.16 for ; Sat, 02 Nov 2013 12:13:35 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <526E20EA.9090203@rempel-privat.de> From: Krishna Chaitanya Date: Sun, 3 Nov 2013 00:43:14 +0530 Message-ID: (sfid-20131102_201339_587318_B50C7620) 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 Sat, Nov 2, 2013 at 10:36 PM, Felipe Contreras wrote: > Sorry for the crappy format (laptop is stuck). > > If the problem is the firmware why does it start working when I > restart the router? I was referring FW on iwlwifi, not the AP's. May be restarting the router triggered some kind of event like Beacon Loss which might have helped the STA to connect. Just guessing. > Plus, I should be seeing this problem with other APs. > And what could Windows be doing differently that doesn't exhibit this problem? Without knowing the root cause it tough to comment these questions :-)