[Madwifi-users] problems configuring a netgear WAG511

[John B. <bel...@cs...>]

Hi,
	I'm trying to get a Netgear WAG511 working, but I'm having 
difficulties associating to an open .b AP in managed mode (I haven't 
tried anything else yet).  I get the following messages when I load the 
driver:

ath_pci: 0.8.2.0 BETA (Sam Leffler <sa...@er...>)
ath_pci: cache line size not set; forcing 4
ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 
24Mbps 36M
bps 48Mbps 54Mbps
ath0: 802.11 address: 00:09:5b:43:31:10
ath0: Atheros 5212: mem=0x10400000, irq=11

The card appears to be recognized fine.  "iwlist ath0 scan" always 
returns "ath0      No scan results".
I've tried manually setting the essid with 'iwconfig ath0 mode managed 
essid "UCSD"', but that doesn't help:

# iwconfig ath0
ath0      IEEE 802.11  ESSID:""
           Mode:Managed  Frequency:2.462GHz  Access Point: 
FF:FF:FF:FF:FF:FF
           Bit Rate:1Mb/s   Tx-Power:off   Sensitivity=0/3
           Retry:off   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off
           Link Quality:0  Signal level:0  Noise level:0
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0

The frequency still changes, indicating the card is scanning.  I've 
also tried forcing the card into .b mode with "iwpriv ath0 mode 2", but 
the card still doesn't find the AP (as an aside "iwpriv ath0 mode 1" 
fails with the error "Interface doesn't accept private ioctl...  mode 
(8BE0): No such device or address" even though the WAG511 supports .a).

Additionally I enabled the debug output from the wlan module and get:

ieee80211_next_scan_R26f8e6a7: chan 10->11
ieee80211_new_state_R6b82432d: SCAN -> SCAN
ieee80211_next_scan_R26f8e6a7: chan 11->1
ieee80211_new_state_R6b82432d: SCAN -> SCAN
ieee80211_next_scan_R26f8e6a7: chan 1->2
ieee80211_new_state_R6b82432d: SCAN -> SCAN
ieee80211_next_scan_R26f8e6a7: chan 2->3
ieee80211_new_state_R6b82432d: SCAN -> SCAN
ieee80211_next_scan_R26f8e6a7: chan 3->4
ieee80211_new_state_R6b82432d: SCAN -> SCAN
ieee80211_next_scan_R26f8e6a7: chan 4->5
ieee80211_new_state_R6b82432d: SCAN -> SCAN
ieee80211_next_scan_R26f8e6a7: chan 5->6
ieee80211_new_state_R6b82432d: SCAN -> SCAN
ieee80211_next_scan_R26f8e6a7: chan 6->7
ieee80211_new_state_R6b82432d: SCAN -> SCAN
ieee80211_next_scan_R26f8e6a7: chan 7->8
ieee80211_new_state_R6b82432d: SCAN -> SCAN
ieee80211_next_scan_R26f8e6a7: chan 8->9
ieee80211_new_state_R6b82432d: SCAN -> SCAN
ieee80211_next_scan_R26f8e6a7: chan 9->10
ieee80211_new_state_R6b82432d: SCAN -> SCAN
ieee80211_end_scan_Rd9685845: no scan candidate

It appears the card is scanning for the AP, but never finds it.

I read about the possibility of missing management frames while 
scanning in the madwifi-devel archive, but there was no resolution.  
Could that be what is happening to me?  Any other thoughts on the 
matter?

Thanks.

-John