On Thu, 18 Mar 2010, Ing. Alexander KrE!ek wrote:

> Same story here.
> 
> After a lot of tries with two different Atheros AR5212/5213 (one CM9 and
> one TP-Link) I bought "Tonze PC-620C" minipci card with Ralink chipset.
> Mission accomplished.

It's not only hostap. I think something gone wrong with ath driver.

This is with

ral0 at pci2 dev 2 function 0 "Ralink RT2561" rev 0x00: irq 10, address 
00:0d:f0:3e:6e:a0
ral0: MAC/BBP RT2561C, RF RT2527

ral0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:0d:f0:3e:6e:a0
        priority: 4
        groups: wlan egress
        media: IEEE802.11 autoselect (OFDM36 mode 11g)
        status: active
        ieee80211: nwid wlancasa chan 11 bssid 00:0c:f6:34:d8:fc 50dB wpapsk 
<not displayed> wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp 
100dBm
        inet6 fe80::20d:f0ff:fe3e:6ea0%ral0 prefixlen 64 scopeid 0x2
        inet 192.168.2.102 netmask 0xffffff00 broadcast 192.168.2.255

While this is with

ath0 at pci2 dev 2 function 0 "Atheros AR5212" rev 0x01: irq 10
ath0: AR5213 5.6 phy 4.1 rf5111 1.7 rf2111 2.3, FCC2A*, address 
00:90:96:9b:e3:7b

ath0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:90:96:9b:e3:7b
        priority: 4
        groups: wlan egress
        media: IEEE802.11 autoselect (DS11 mode 11b)
        status: active
        ieee80211: nwid wlancasa chan 11 bssid 00:0c:f6:34:d8:fc wpapsk <not 
displayed> wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp
        inet6 fe80::290:96ff:fe9b:e37b%ath0 prefixlen 64 scopeid 0x2
        inet 192.168.2.103 netmask 0xffffff00 broadcast 192.168.2.255

Setup is exactly the same: same ap, same environment, same distance from
the ap... I've only swapped cards.

Maybe is it related to this bug reported in the ath(4) manpage?

Performance in lossy environments is suboptimal. The algorithm used to
select the rate for transmitted packets is very simplistic. There is
no software retransmit; only hardware retransmit is used.


Cheers,
David

Reply via email to