*** This bug is a duplicate of bug 208306 ***
https://bugs.launchpad.net/bugs/208306
** This bug has been marked a duplicate of bug 208306
[ath_pci] cannot connect to hidden ap
--
[gutsy] ath_pci not running well w/ 11g
https://bugs.launchpad.net/bugs/139391
You received this bug notifica
This is a Network Manager bug.
Fix released for Hardy.
Marking as duplicate.
Any backport requests should be first examined against:
https://help.ubuntu.com/community/UbuntuBackports
Then filed against the main bug stream. Unless this duplicate message is viewed
as errant. In which case please
On the 11g front, the latest svn snapshot of madwifi trunk worked fine
11g on my WPA2 home box, but didn't work at all for LEAP (i.e.
regressed). I'm going to try ndiswrapper as my solution, that works at
home, will see about LEAP networks on monday.
--
[gutsy] ath_pci not running well w/ 11g
ht
I did digging in the driver, and found that line 868 of
ieee80211_input.c was the part giving the message, traced the
node_is_authorized and found that exceptions are made for 8021X (LEAP
notably). I didn't dig deep as to how a node was to be authorized in
8021X as opposed to WPA2, so I just noted
To follow up, on the dhclient failure, I do see this if I enablesufficient
debug:
Sep 14 09:33:47 vorfeed kernel: [ 2777.084000] [ath0:00:05:4e:45:d8:42] discard
data frame, unauthorized port: ether type 0x800 len 92
Sep 14 09:33:48 vorfeed kernel: [ 2777.704000] [ath0:00:d0:05:9d:64:0a] discard
