Hi,
Yesterday I ran into a "no traffic" situation, which was not resolveable by unloading the wl module:
tcpdump on the wlan0 interface showed me only:
00:21:21.575404 EAPOL key (3) v2, len 117
00:21:21.865239 EAPOL key (3) v2, len 117
00:21:22.385278 EAPOL key (3) v2, len 11
...
At the same I was able to use the same (hotel) accesspoint with my android phone without trouble. After a reboot (and a update to 4.1.4), the Wifi worked.
One observation: I remember the kde network manager thing telling me the Wifi was "WPA" while it was not able to connect. After the reboot the working variant is WPA2-PSK. Maybe the wpa-supplicant got wrong info from the driver (via cfg802 ????)
Hi,
Yesterday I ran into a "no traffic" situation, which was not resolveable by unloading the wl module:
tcpdump on the wlan0 interface showed me only:
00:21:21.575404 EAPOL key (3) v2, len 117
00:21:21.865239 EAPOL key (3) v2, len 117
00:21:22.385278 EAPOL key (3) v2, len 11
...
At the same I was able to use the same (hotel) accesspoint with my android phone without trouble. After a reboot (and a update to 4.1.4), the Wifi worked.
One observation: I remember the kde network manager thing telling me the Wifi was "WPA" while it was not able to connect. After the reboot the working variant is WPA2-PSK. Maybe the wpa-supplicant got wrong info from the driver (via cfg802 ????)
rgds,
j