Return-path: Received: from mail-ey0-f174.google.com ([209.85.215.174]:59362 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752007Ab0JYTbE (ORCPT ); Mon, 25 Oct 2010 15:31:04 -0400 Received: by eye27 with SMTP id 27so4558595eye.19 for ; Mon, 25 Oct 2010 12:31:03 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1287995967.3587.9.camel@jlt3.sipsolutions.net> Date: Mon, 25 Oct 2010 12:31:02 -0700 Message-ID: Subject: Re: Modifying the driver iwlwifi From: Blaise Gassend To: "Cassiano Tartari, Eng." Cc: Johannes Berg , linux-wireless@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: > How can I know if a AP is "compliant/certified" ? I'm such a newbie. I suspect that most of them are. If they have a WiFi logo on the box they should be: http://www.wi-fiplanet.com/tutorials/article.php/2203361/Wi-Fi-Interoperability-Compliance-Steps.htm >> I had a look at the paper, and the original poster seems to have >> exaggerated the paper's claims. They do indeed do the authentication >> and association request before getting responses. For everything else, >> they wait to get the response for the previous stage. The main >> difference is that they greatly reduce the timeouts before retrying at >> each stage. The paper is also limited to non-encrypted networks. > > My objetive in my current job is just that, reduce the time of authentication. > > Someone has a better idea or solution to reduce the association time? > I need to use DHCP and could be a open network. How short does it need to be for you? In my experience sub-second is pretty if you know the frequency, have low packet loss, and have an aggressive DHCP client. The methods in the paper should make it work even with higher packet loss.