[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ATH driver doesn't associate with turbo.

[Please do not send me mail and cc a mailing list; I read most fbsd mailing 

On Tuesday 13 January 2004 07:43 am, Randy Bush wrote:
> thinkpad t40p current as of 6 jan (real current has fatal ata crashes)
>     ath0: <Atheros 5211> mem 0xc0210000-0xc021ffff irq 11 at device 2.0 on
> pci2 ath0: mac 4.2 phy 3.0 5ghz radio 1.7 2ghz radio 2.3
>     ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
>     ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
>     ath0: 802.11 address: 00:05:4e:41:ee:cd
> nokia ap with orinoco gold card on chan 11
> netgear he102 802.11a ap on chan 52 (5.26GHz)
> all on same ssid
> sometimes ath0 associates with one ap, sometimes the other, and it
> will switch from 11a to 11b and not come back to 11a.  e.g., right
> now it says
>     # ifconfig ath0
>     ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> 	    inet netmask 0xffffff00 broadcast
> 	    ether 00:05:4e:41:ee:cd
> 	    media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps)
> 	    status: associated
> 	    ssid rgnet-home 1:rgnet-home
> 	    channel 11 authmode OPEN powersavemode OFF powersavesleep 100
> 	    wepmode OFF weptxkey 1
> 	    wepkey 1:104-bit
> i suspect the ath driver, as i do not see similar issues in winxp.
> but of course, when debugging, i am not sure of anything.

The 802.11 code scans all channels by default.  It does not, for example, 
stick to a band where it finds an AP.  If you want to constrain it's search 
to a particular band use something like 

ifconfig ath0 mode 11a

If that doesn't answer what you were asking try adding a "?" somewhere :)


Visit your host, monkey.org