On Sun, Jul 24, 2011 at 8:55 AM, Daniel Melameth <[email protected]> wrote:
> I recently picked up another notebook and the ath card in it cannot
> see my SSIDs (meth, meth2.4 and open) at home.  However, my two other
> notebooks, one using iwi and other other running Windows, can see
> these just fine (and all three notebooks are next to each other).  The
> following is an ifconfig scan from both 4.8-stable machines, but the
> issue is also reproducible with a snapshot--any ideas appreciated.
>
> iwi0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
>        lladdr 00:13:ce:c7:e4:f6
>        priority: 4
>        groups: wlan egress
>        media: IEEE802.11 autoselect
>        status: no network
>        ieee80211: nwid meth2.4 wpapsk [redacted] wpaprotos wpa1,wpa2
> wpaakms psk wpaciphers tkip,ccmp wpagroupcipher tkip 100dBm
>                nwid wings chan 11 bssid 00:1e:2a:05:26:8c 51dB 54M
> privacy,short_preamble,short_slottime
>                nwid patrice chan 11 bssid 00:1e:e5:78:48:78 36dB 54M
> privacy,short_slottime
>                nwid Juventus12 chan 1 bssid 40:4a:03:dd:a5:55 43dB
> 54M privacy,short_preamble,short_slottime
>                nwid JadeMoose chan 6 bssid 68:7f:74:9d:64:29 58dB 54M
> privacy,short_slottime
>                nwid JadeMoose-guest chan 6 bssid 68:7f:74:9d:64:2a
> 59dB 54M short_slottime
>                nwid meth chan 10 bssid ac:a0:16:85:f7:00 70dB 54M
> privacy,spectrum_mgmt
>                nwid meth2.4 chan 9 bssid ac:a0:16:ba:fc:b0 71dB 54M
> privacy,short_preamble
>                nwid open chan 9 bssid ac:a0:16:ba:fc:b1 73dB 54M
short_preamble
>                nwid Wireless chan 6 bssid e0:91:f5:b3:62:64 61dB 54M
> privacy,short_preamble,short_slottime
>
> ath0: flags=8822<BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST> mtu 1500
>        lladdr 00:05:4e:51:1d:a4
>        priority: 4
>        groups: wlan
>        media: IEEE802.11 autoselect
>        status: no network
>        ieee80211: nwid ""
>                nwid "" chan 11 bssid 00:00:00:00:00:00 0% 54M
short_slottime
>                nwid wings chan 11 bssid 00:1e:2a:05:26:8c 0% 54M
> privacy,short_preamble,short_slottime
>                nwid patrice chan 11 bssid 00:1e:e5:78:48:78 0% 54M
> privacy,short_slottime
>                nwid qwest9941 chan 1 bssid 00:24:37:10:3f:f0 0% 54M
> privacy,short_slottime
>                nwid Lockton-Private chan 11 bssid 00:24:6c:11:f3:f0
> 0% 54M privacy,short_preamble,short_slottime
>                nwid Lockton-Guest chan 11 bssid 00:24:6c:11:f3:f1 0%
> 54M short_preamble,short_slottime
>                nwid Sevjan chan 4 bssid 00:24:b2:e0:64:e1 0% 54M
> privacy,short_preamble,short_slottime
>                nwid Juventus12 chan 1 bssid 40:4a:03:dd:a5:55 0% 54M
> privacy,short_preamble,short_slottime
>                nwid JadeMoose chan 6 bssid 68:7f:74:9d:64:29 0% 54M
> privacy,short_slottime
>                nwid JadeMoose-guest chan 6 bssid 68:7f:74:9d:64:2a 0%
> 54M short_slottime
>                nwid SharonRoth chan 2 bssid a0:21:b7:a1:20:ba 0% 54M
> privacy,short_preamble
>                nwid Wireless chan 6 bssid e0:91:f5:b3:62:64 0% 54M
> privacy,short_preamble,short_slottime

Upon further analysis, it appears ath has an issue with APs that do
not send beacons at 11b rates--and this is only obsernable with
OpenBSD as the issue is not reproducible with the same card under
Windows.  Reconfiguring my Cisco AP to allow non-OFDM rates allows ath
to see the SSIDs, but this also allows the AP to serve 11b clients,
which is not desirable.

Anyone else experiencing this?

Reply via email to