On Fri, May 23, 2008 at 1:33 AM, Vincent C Jones <v.jones@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > On Thu, 2008-05-22 at 19:53 +0300, Tomas Winkler wrote: >> On Mon, May 12, 2008 at 9:37 PM, Vincent C Jones >> <v.jones@xxxxxxxxxxxxxxxxxxxxxxx> wrote: >> > >> > On Mon, 2008-05-12 at 19:50 +0300, Tomas Winkler wrote: >> > >> >> Meanwhile we've reproduced the wpa_supplicant issue... >> >> >> > >> > That is great news. Let me know when it is time to test again... >> >> Please try this one. I've just pasted that in so it's might be >> white-space-wise broken >> >> diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c >> index 7877d3b..5996e3d 100644 >> * * * >> Tomas > > Tomas, > > Applied patch to today's > git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git > and I can confirm that wpa_supplicant v0.6.3 again works on the A band. > > FWIW, however, I still have some issues: > > 1 - Roaming from 3com to NetGear takes about 5 minutes before iwlist > scan sees the A/N channel on the NetGear AP. Roaming from NetGear to > 3com, however, the 3com AP is seen on the first scan after losing > contact. What channel is NG?, what is the beacon period. We'll soon release a new uCode that should speed up a bit scanning on A band. > 2 - The NetGear is allegedly 11n, but shows up as standard A (or G) in > iwconfig et al. Highest data rate listed by iwlist is 54 on A, 48 on G. wext doesn't report 11n rates and probably never will, it doesn't mean there is no 11n connection. Currently I don't have some non crypto interface looking into it. > 3 - Booting Windows, the 4965 does see the NetGear as 802.11n, so I > can't blame it on the hardware... > No you cant :) > 4 - I won't guarantee it is not a configuration issue on my part... > attached is the ".config" file used to compile the kernel. > Looks good. Tomas -- 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
