The deauth reason code isn't passed up to the supplicant, so the supplicant
doesn't have the best info to make a decision. If the notification message
was changed to include the reason code, then the supplicant wouldn't need to
do a scan in this case, which makes everything faster (unless you have
accurate scan results from a background scan). Dropping a scan means
everything works much faster.
Background scans probably won't work for our app because we are transmitting
about 2-3 (sometimes more) good sized data packets every ~40 msec. We would
have to drop video frames to make room for background scanning, but that
degrades the video quality, and that is noticeable.
Chuck
----- Original Message -----
From: "Johannes Berg" <johannes@xxxxxxxxxxxxxxxx>
To: "Chuck Crisler" <ccrisler@xxxxxxxxxx>
Cc: <linux-wireless@xxxxxxxxxxxxxxx>
Sent: Tuesday, January 18, 2011 10:23 AM
Subject: Re: intermittent eap authentication failure
On Tue, 2011-01-18 at 10:21 -0500, Chuck Crisler wrote:
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?
I don't think there's any design here, and in any case that's
wpa_supplicant's doing. :)
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
--
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
