Some AR5212 chips seem to have problems, even though they are detected by OpenBSD. I read something about newer firmwares? Try searching the archives. One person recently reported having success by setting COUNTRYCODE to "de" and rebuilding his kernel; it didn't work for me but I guess it's worth a shot.
Good luck. As this is not a tech@ topic I've moved it back to [EMAIL PROTECTED] -Ray- On Thu, Jan 12, 2006 at 11:24:41PM -0500, [EMAIL PROTECTED] wrote: > I apologize for the cross-post, but since this has gone unanswered on > misc@ for 3+ days, I figured that it was unlikely to ever get a > response there. > > -------------------- > > Hello All, > > I've got a Linksys WMP55AG that's refusing to see my wireless network. While > it's entirely possible that I've misconfigured it, given other somewhat > recent > posts I've seen about problems with ath devices (i.e. > http://marc.theaimsgroup.com/?l=openbsd-misc&m=113166150212987&w=2), I > figure > it's also possible that there's some sort of a driver bug, which I'd like to > help fix if it exists. > > My setup should be relatively straightforward: I've got a 3.7-stable system > running a National Datacomm NCP130 as an access point. Its relevant info is: > > dmesg: > wi0 at pci0 dev 12 function 0 "National Datacomm Corp NCP130 Rev A2" > rev 0x01: irq 9 > wi0: PRISM2 HWB3163 rev.B, Firmware 0.3.0 (primary), 1.7.1 (station), > address > 00:80:c6:e3:72:2c > > wicontrol wi0 output: > NIC serial number: [ 99SA01000000 ] > Station name: [ WaveLAN/IEEE node ] > SSID for IBSS creation: [ kirknet ] > Current netname (SSID): [ kirknet ] > Desired netname (SSID): [ kirknet ] > Current BSSID: [ 00:80:c6:e3:72:2c ] > Channel list: [ 2047 ] > IBSS channel: [ 3 ] > Current channel: [ 3 ] > Comms quality/signal/noise: [ 0 81 27 ] > Promiscuous mode: [ Off ] > Process 802.11b Frame: [ Off ] > Port type (1=BSS, 3=ad-hoc, 6=Host AP): [ 6 ] > MAC address: [ 00:80:c6:e3:72:2c ] > TX rate (selection): [ 3 ] > TX rate (actual speed): [ 2 ] > Maximum data length: [ 2304 ] > RTS/CTS handshake threshold: [ 2347 ] > Create IBSS: [ Off ] > Antenna diversity (0=auto,1=pri,2=aux): [ ] > Microwave oven robustness: [ On ] > Roaming mode(1=firm,3=disable): [ 1 ] > Access point density: [ 1 ] > Power Management: [ Off ] > Max sleep time: [ 100 ] > Enhanced Security mode: [ 0 ] > Intersil Prism2-based card: [ 1 ] > Card info: [ PRISM2 HWB3163 rev.B, > Firmware 1.7.1 ] > Encryption: [ On ] > Encryption algorithm: [ Firmware WEP ] > Authentication type > (1=OpenSys, 2=Shared Key): [ 2 ] > TX encryption key: [ 1 ] > Encryption keys: [ <not shown> ][ ][ ][ ] > > ifconfig: > wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > address: 00:80:c6:e3:72:2c > ieee80211: nwid kirknet nwkey <not shown> -11dBm (auto) > media: IEEE802.11 autoselect hostap (DS2) > status: active > inet 192.168.1.42 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::280:c6ff:fee3:722c%wi0 prefixlen 64 scopeid 0x3 > > Several clients with different OSes connect to this AP without hassle, > including > WinXP SP2, OS X 10.2.8, and Ubuntu's 5.10 release (a 2.6.12 Linux kernel), > so > clearly the access point is working. > > My client with the Linksys card shows the following from dmesg: > > ath0 at pci1 dev 10 function 0 "Atheros AR5212" rev 0x01: irq 11 > ath0: AR5213 5.6 phy 4.1 rf5111 1.7 rf2111 2.3, FCC1A, address > 00:0c:41:16:cb:d4 > > Going along with "man ath", I figured I could just run "ifconfig ath0 nwid > kirknet nwkey <my key>" and be good to go. After doing so, I can see that > the > card has picked up the right AP and channel; unfortunately, however, it > thinks > it's not connected to the network: > > ath0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:0c:41:16:cb:d4 > media: IEEE802.11 autoselect mode 11b (DS1 mode 11b) > status: no network > ieee80211: nwid kirknet chan 3 bssid 00:80:c6:e3:72:2c nwkey <my > key> > inet 192.168.1.101 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::20c:41ff:fe16:cbd4%ath0 prefixlen 64 scopeid 0x2 > > What's particularly strange is the output of "wicontrol wi0 -l" on the > access point: > > 00:04:23:4b:38:fd asid=02d0, flags=3<AUTH,ASSOC>, > caps=31<ESS,PRIVACY,SHORT_PREAMBLE>, rates=f<1M,2M,5.5M,11M>, sig=35/14 > 00:30:65:11:35:b0 asid=0140, flags=3<AUTH,ASSOC>, caps=11<ESS,PRIVACY>, > rates=f<1M,2M,5.5M,11M>, sig=45/13 > 00:0c:41:16:cb:d4 asid=0620, flags=0<>, caps=0<>, rates=0<> > 00:0c:41:14:3c:f7 asid=0650, flags=3<AUTH,ASSOC>, > caps=431<ESS,PRIVACY,SHORT_PREAMBLE,SHORT_SLOTTIME>, > rates=f<1M,2M,5.5M,11M>, > sig=40/255 > > It's almost as if my Linksys card isn't sending proper associative > information > along to the AP, since it has blank "<>"s where the other three functional > systems have information about flags, rates, etc. > > The box with the Linksys is running the most current snapshot (Jan. 7, > 2006), > downloaded directly from ftp.openbsd.org; I upgraded from 3.8-release in the > hopes that there were recent fixes that might solve this problem. > > If anyone can point out something I've missed or done incorrectly, I'd love > to > hear it (BTW, I've tried setting the media type on my Linksys card manually > to > match the AP, as well as setting the mode to 11b, with no success). If this > is > indicative of some sort of a problem with the ath driver, I'd be interested > in > working with any relevant developer(s) to fix the problem, including taking > a > look at the source myself if someone who doesn't have the time to fix it > themself pointed me in the general direction of where the problem might be. > > Alex Kirk
