I continued my tests and researchs, and found that my problem is much
like the one in
http://comments.gmane.org/gmane.linux.drivers.ath9k.devel/7149 : the
part reboot the box, connect to it the first does indeed the job. It's
very annoying, but maybe this is exclusive for this particular wifi
** Summary changed:
- 168c:002b Ath9k wifi problems
+ 168c:002b Ath9k wifi does not connect to WPA+TKIP, does to WPA+AES
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031332
Title:
168c:002b
On Tue, Jul 31, 2012 at 10:15 PM, Christopher M. Penalver
christopher.penal...@gmx.com wrote:
** Summary changed:
- 168c:002b Ath9k wifi problems
+ 168c:002b Ath9k wifi does not connect to WPA+TKIP, does to WPA+AES
I'm not fully convinced this is the case, as per my bad experience
this night.
