Prioritizing authentication pkts & resending failed EAPOL pkts?

[Ben Greear]

While testing 128 stations against an ath9k VAP, I am seeing problems where
only around half of them can actually authenticate.

I am sending about 20kbps of traffic on anything that is authenticated, and
reported latencies there are multiple seconds.  (Not sure why, it should
have enough bandwidth..maybe too much auth attempt traffic & scanning
is causing issues..)

So first question:  Is the auth traffic prioritized over regular traffic?

Second:  Any idea how to go about fixing up the retransmit logic per
this TODO:

		/* TODO: re-send EAPOL-Key couple of times (with short delay
		 * between them?). If all attempt fail, report error and
		 * deauthenticate STA so that it will get new keys when
		 * authenticating again (e.g., after returning in range).
		 * Separate limit/transmit state needed both for unicast and
		 * broadcast keys(?) */

Here's a filtered part of the log showing ack-failure msgs...

1296763802.180575: 1296763802.365012: IEEE 802.1X: 00:0c:42:61:00:78 TX status - version=2 type=3 length=95 - ack=0
1296763802.365065: 1296763802.365121: IEEE 802.1X: 00:0c:42:61:00:77 TX status - version=2 type=3 length=95 - ack=0
1296763802.365157: 1296763802.365192: IEEE 802.1X: 00:0c:42:61:00:76 TX status - version=2 type=3 length=95 - ack=0
1296763802.365220: 1296763802.365254: IEEE 802.1X: 00:0c:42:61:00:65 TX status - version=2 type=3 length=95 - ack=0
1296763802.365281: 1296763802.365314: IEEE 802.1X: 00:0c:42:61:00:75 TX status - version=2 type=3 length=95 - ack=0
1296763802.365342: 1296763802.365375: IEEE 802.1X: 00:0c:42:61:00:78 TX status - version=2 type=3 length=95 - ack=0
1296763802.365403: 1296763802.365436: IEEE 802.1X: 00:0c:42:61:00:77 TX status - version=2 type=3 length=95 - ack=0
1296763802.365464: 1296763802.365498: IEEE 802.1X: 00:0c:42:61:00:76 TX status - version=2 type=3 length=95 - ack=0
1296763802.365555: 1296763802.365589: IEEE 802.1X: 00:0c:42:61:00:65 TX status - version=2 type=3 length=95 - ack=0
1296763802.365617: 1296763802.365650: IEEE 802.1X: 00:0c:42:61:00:75 TX status - version=2 type=3 length=95 - ack=0
1296763803.020316: IEEE 802.1X: 00:0c:42:61:00:78 TX status - version=2 type=3 length=95 - ack=0
1296763803.020374: 1296763803.053300: IEEE 802.1X: 00:0c:42:61:00:77 TX status - version=2 type=3 length=95 - ack=0
1296763803.053341: 1296763803.071921: IEEE 802.1X: 00:0c:42:61:00:76 TX status - version=2 type=3 length=95 - ack=0
1296763803.071962: 1296763803.088045: IEEE 802.1X: 00:0c:42:61:00:65 TX status - version=2 type=3 length=95 - ack=0
1296763803.088084: 1296763803.105268: IEEE 802.1X: 00:0c:42:61:00:75 TX status - version=2 type=3 length=95 - ack=0
1296763804.021273: IEEE 802.1X: 00:0c:42:61:00:78 TX status - version=2 type=3 length=95 - ack=0
1296763804.021316: 1296763804.036810: IEEE 802.1X: 00:0c:42:61:00:77 TX status - version=2 type=3 length=95 - ack=0
1296763804.036851: 1296763804.058187: IEEE 802.1X: 00:0c:42:61:00:76 TX status - version=2 type=3 length=95 - ack=0
1296763804.058232: 1296763804.460057: IEEE 802.1X: 00:0c:42:61:00:65 TX status - version=2 type=3 length=95 - ack=0
1296763804.460124: 1296763804.507827: IEEE 802.1X: 00:0c:42:61:00:75 TX status - version=2 type=3 length=95 - ack=0

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com