On 15-08-17 10:22, Russell King - ARM Linux wrote:
On Mon, Aug 14, 2017 at 11:25:03PM -0700, rosenp@xxxxxxxxx wrote:
If using rtlwifi, you could try using rtl8xxxu and see if you get
similar results. ¯\_(ツ)_/¯
I'm using rtl8xxxu. I don't think rtlwifi supports the 8192eu - it
certainly does not list the device id:
Bus 001 Device 002: ID 0bda:818b Realtek Semiconductor Corp.
As an extra data point, trying to associate to the 4330 with an Intel
client gives:
[8821752.691490] wlan0: authenticate with 6c:ad:f8:1d:4c:d9
[8821752.693448] wlan0: send auth to 6c:ad:f8:1d:4c:d9 (try 1/3)
[8821752.696230] wlan0: authenticated
[8821752.697493] wlan0: associate with 6c:ad:f8:1d:4c:d9 (try 1/3)
[8821752.700816] wlan0: RX AssocResp from 6c:ad:f8:1d:4c:d9 (capab=0x411 status=0 aid=1)
[8821752.704407] wlan0: associated
[8821755.814844] wlan0: deauthenticated from 6c:ad:f8:1d:4c:d9 (Reason: 2=PREV_AUTH_NOT_VALID)
which gets slightly further but ultimately still fails.
Hi Russell,
On vacation this week, but it is raining over here so have some moments
to kill. Here a couple of things to try:
1) try without encryption.
2) does hostapd log show anything interesting.
3) can you use the Intel client to make a sniff.
I can check what could trigger the firmware after 3 sec. to deauth. Just
not sure if I will get to that this week. Could be failing EAPOL handshake.
Regards,
Arend
