linux-kernel - Re: REGRESSION: v3.2-rcX: iwlagn refuses to associate with my AP's

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 13 Dec 2011 19:14:30 -0800
From:	"Guy, Wey-Yi" <wey-yi.w.guy@...el.com>
To:	Ted Ts'o <tytso@....edu>
Cc:	Johannes Berg <johannes@...solutions.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: Re: REGRESSION: v3.2-rcX: iwlagn refuses to associate with my AP's

Hi Ted,
On Tue, 2011-12-13 at 17:59 -0800, Ted Ts'o wrote:
> On Tue, Dec 13, 2011 at 03:17:52PM -0500, Ted Ts'o wrote:
> > Well, this patch seems to fix things for the non-authenticated case.
> > I can now associate with the GoogleGuest SSID without any problems.
> > I'm still having problems associating with the EAP-TLS encrypted
> > network, but that looks like it's a different bug.  (And that may
> > explain why I had so much trouble bisecting this; there are two issues
> > that have very similar symptoms.)
> 
> ... and the second problem I had with associating with EAP-TLS
> encrypted SSID's was solved by Wey-Yi's patch: 
> 
> 	  iwlwifi: allow to switch to HT40 if not associated yet
> 
> ... found in the thread "iwlagn regression in v3.1.5"
> 
> So with these two patches applied, things are now stable for me.
> 
> One thing: out of curiosity, I assume there is a pretty good testing
> infrastructure at Intel --- how was it that this didn't caught
> earlier?  Is it because different access points do things a little
> different?  Would it be useful if I can find out the model of access
> point that we're using, so you could hopefully augment your library of
> test hardware?  I'm asking out of purely selfish reasons, of course,
> since this took me the better part of a day to bisect each of these
> problems.

You ask a very valid and good question, you are correct, we at Intel
have a very good lab and great testing infrastructure. But at the same
time, there are so many APs available on the market and each one could
behave differently, also just like station, AP's software continue
change and improve, and at the same time, bugs can be introduced. We try
to do our best, but we can not cover everything and we truly hope the
community can help us flush the corner cases and bugs we miss.

Yes, if you can let us know your configuration and the AP information,
it will be very helpful. But please do help us continue test our latest
driver, so we can improve our driver quality and better serve the
community.

Thanks
Wey 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/