Adding linux-wireless, not sure if many people read this list. Luis On Tue, Mar 26, 2013 at 8:40 AM, Jouni Malinen <jouni@xxxxxxxxxxxxxxxx> wrote: > On Tue, Mar 26, 2013 at 08:25:20AM -0700, Linus Torvalds wrote: >> Ok, added to the bugzilla. I'm still in the condo, but I'm leaving >> soon and need to pack up, so this is likely the last thing I can do.. >> >> It is indeed the nl80211 part that causes problems, so I guess we're >> back to an actual ath9k issue. > > Thanks. This is peculiar, but indeed pretty clear on the issue being > triggered by use of nl80211 instead of WEXT regardless of what the > actual issue is. I haven't used wpa_supplicant v1.0-rc3 pretty much > at all myself and there has been quite a few changes in nl80211 > interaction since then. Anyway, this should give a good test case with > the current kernel and that somewhat older version with nl80211 > implementation in wpa_supplicant. > >> > In addition, you could try to collect the frames exchanged by the >> > success and failure cases using a monitor interface: >> > >> > iw wlan0 interface add mon0 type monitor >> > ifconfig mon0 up >> > dumpcap -i mon0 -w /tmp/capture.pkt >> > >> > And then run the success/failure case. >> >> Ok, will try to do that too. > > If you'll get a chance to do that, it would be quite helpful since it > could make it easier to try to reproduce this if there is indeed > something special about that AP behavior that allows the issue to show > up but does not show up in the wpa_supplicant debug log. > > -- > Jouni Malinen PGP id EFC895FA > _______________________________________________ > ath9k-devel mailing list > ath9k-devel@xxxxxxxxxxxxxxx > https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
