What is the reason that the design calls for a scan in response to a session
timeout? A session timeout doesn't happen because of a roam, so the original
AP is probably still good. Why scan?
Chuck
----- Original Message -----
From: "Johannes Berg" <johannes@xxxxxxxxxxxxxxxx>
To: "Chuck Crisler" <ccrisler@xxxxxxxxxx>
Cc: <linux-wireless@xxxxxxxxxxxxxxx>
Sent: Tuesday, January 18, 2011 9:57 AM
Subject: Re: intermittent eap authentication failure
On Tue, 2011-01-18 at 09:54 -0500, Chuck Crisler wrote:
I will have to reply later about why it is associating. I will have to
add a
printk to my driver but I currently have 2 tests running and don't want
to
stop either.
It looks like it might be called by ieee80211_sta_work() in mlme.c
because
it might still be in the IEEE80211_STA_MLME_ASSOCIATE state. I will
confirm
that.
Did you ever consider using compat-wireless? Frankly, my main memory
isn't large enough to hold information about old mac80211 behaviour so I
have to get that information from swap (git tree) and that's really
slow :-)
johannes
--
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
