Re: Performance of AR9287
.. and yes, what I'd really like to do is find someone who wants to look after "long distance links" with atheros hardware (and has the kit to do so!) and help me fix up the coverage class code to work in a more generic fashion, for all chips. I can tell people what to do if they'd like to hack on this (specifically look at ah_coverageClass, and ar5212SetCoverageClass()) and I can help them with the math, I just don't have the time to make it all work right. :-) Adrian On 22 September 2012 12:33, Adrian Chadd wrote: > Ah. athctrl.sh ? > > > > > adrian > > On 22 September 2012 02:04, Johann Hugo wrote: >> I'm still using a utility from Sam. >> >> >> >> athctrl -d 8000 >> >> Setup IFS parameters on interface ath0 for 8000 meter p-2-p link >> >> dev.ath.0.slottime=36 >> >> dev.ath.0.acktimeout=75 >> >> dev.ath.0.ctstimeout=75 >> >> >> >> Are these settings still good ? >> >> >> >> Are there any way do detect these automatically ? >> >> >> >> Johann >> >> >> >> On Saturday 22 September 2012 10:24:43 Adrian Chadd wrote: >> >>> I assume you've tweaked the ack, slot, rtsctstimeout? >> >>> >> >>> The 11n rate control code is a little more jumpy. I've fixed that in >> >>> recent checkins. It's not optimal but now it's not as jumpy as before. >> >>> >> >>> Update to -HEAD, then use 'athratestats' on the peer MAC address. It's >> >>> quite useful to see what's actually going on. :-) >> >>> >> >>> >> >>> >> >>> Adrian >> >>> >> >>> On 22 September 2012 01:20, Johann Hugo wrote: >> >>> > On Saturday 22 September 2012 02:05:23 Derrick Edwards wrote: >> >>> >> Thanks again for looking into this. >> >>> >> >> >>> >> My main concern was the range of network performance that I was getting >> >>> >> >> >>> >> when the laptop was right in front of the access point. As you can see >> >>> >> >> >>> >> bandwith varied greatly. >> >>> > >> >>> > I don't know if it's related, but my RSSI and RATE jumps around quite a >> >>> > lot while transfering a large file. >> >>> > >> >>> > >> >>> > >> >>> > Output from loop doing "ifconfig wlan0 list sta" while transfering a big >> >>> > file. >> >>> > >> >>> > >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 86M 16.5 0 842 9440 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 43M 12.5 0 1063 14784 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 43M 15.5 0 1362 21088 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 86M 15.5 0 1627 27488 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 86M 13.5 0 2150 38976 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 86M 11.5 0 2289 42384 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 29M 24.5 0 3075 60016 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 86M 28.5 0 3369 1600 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 86M 14.0 0 3839 11744 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 29M 13.5 0 87 19936 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 58M 11.5 0 403 27440 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 58M 12.5 0 758 35200 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 58M 11.0 0 1054 42320 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 58M 23.5 0 1249 46512 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 29M 11.0 0 1381 49312 E AQHTR HTCAP WME >> >>> > >> >>> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >> >>> > >> >>> > 00:0c:42:6c:58:29 1 128 58M 11.5 0 1584 54224 E AQHTR HTCAP WME >> >>> > >> >>> > >> >>> > >> >>> > System info = hybrid >> >>> > >> >>> > HW = gateworks ARM >> >>> > >> >>> > OS = FreeBSD-9 with ath code from current >> >>> > >> >>> > Wifi = RouterBOARD R52nM = AR9220 >> >>> > >> >>> > Distance = 8km >> >>> > >> >>> > >> >>> > >> >>> > B.t.w if I use the same HW with FreeBSD-9 in 11a mode, then RSSI does >>> > not >> >>> > jump around and I get about the same throuput as with N. >> >>> > >> >>> > >> >>> > >> >>> > I don't hav
Re: Performance of AR9287
Ah. athctrl.sh ? adrian On 22 September 2012 02:04, Johann Hugo wrote: > I'm still using a utility from Sam. > > > > athctrl -d 8000 > > Setup IFS parameters on interface ath0 for 8000 meter p-2-p link > > dev.ath.0.slottime=36 > > dev.ath.0.acktimeout=75 > > dev.ath.0.ctstimeout=75 > > > > Are these settings still good ? > > > > Are there any way do detect these automatically ? > > > > Johann > > > > On Saturday 22 September 2012 10:24:43 Adrian Chadd wrote: > >> I assume you've tweaked the ack, slot, rtsctstimeout? > >> > >> The 11n rate control code is a little more jumpy. I've fixed that in > >> recent checkins. It's not optimal but now it's not as jumpy as before. > >> > >> Update to -HEAD, then use 'athratestats' on the peer MAC address. It's > >> quite useful to see what's actually going on. :-) > >> > >> > >> > >> Adrian > >> > >> On 22 September 2012 01:20, Johann Hugo wrote: > >> > On Saturday 22 September 2012 02:05:23 Derrick Edwards wrote: > >> >> Thanks again for looking into this. > >> >> > >> >> My main concern was the range of network performance that I was getting > >> >> > >> >> when the laptop was right in front of the access point. As you can see > >> >> > >> >> bandwith varied greatly. > >> > > >> > I don't know if it's related, but my RSSI and RATE jumps around quite a > >> > lot while transfering a large file. > >> > > >> > > >> > > >> > Output from loop doing "ifconfig wlan0 list sta" while transfering a big > >> > file. > >> > > >> > > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 86M 16.5 0 842 9440 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 43M 12.5 0 1063 14784 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 43M 15.5 0 1362 21088 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 86M 15.5 0 1627 27488 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 86M 13.5 0 2150 38976 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 86M 11.5 0 2289 42384 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 29M 24.5 0 3075 60016 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 86M 28.5 0 3369 1600 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 86M 14.0 0 3839 11744 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 29M 13.5 0 87 19936 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 58M 11.5 0 403 27440 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 58M 12.5 0 758 35200 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 58M 11.0 0 1054 42320 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 58M 23.5 0 1249 46512 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 29M 11.0 0 1381 49312 E AQHTR HTCAP WME > >> > > >> > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > >> > > >> > 00:0c:42:6c:58:29 1 128 58M 11.5 0 1584 54224 E AQHTR HTCAP WME > >> > > >> > > >> > > >> > System info = hybrid > >> > > >> > HW = gateworks ARM > >> > > >> > OS = FreeBSD-9 with ath code from current > >> > > >> > Wifi = RouterBOARD R52nM = AR9220 > >> > > >> > Distance = 8km > >> > > >> > > >> > > >> > B.t.w if I use the same HW with FreeBSD-9 in 11a mode, then RSSI does >> > not > >> > jump around and I get about the same throuput as with N. > >> > > >> > > >> > > >> > I don't have any athstats output, still working on it. > >> > > >> > > >> > > >> > Johann > > r ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Performance of AR9287
I'm still using a utility from Sam. athctrl -d 8000 Setup IFS parameters on interface ath0 for 8000 meter p-2-p link dev.ath.0.slottime=36 dev.ath.0.acktimeout=75 dev.ath.0.ctstimeout=75 Are these settings still good ? Are there any way do detect these automatically ? Johann On Saturday 22 September 2012 10:24:43 Adrian Chadd wrote: > I assume you've tweaked the ack, slot, rtsctstimeout? > > The 11n rate control code is a little more jumpy. I've fixed that in > recent checkins. It's not optimal but now it's not as jumpy as before. > > Update to -HEAD, then use 'athratestats' on the peer MAC address. It's > quite useful to see what's actually going on. :-) > > > > Adrian > > On 22 September 2012 01:20, Johann Hugo wrote: > > On Saturday 22 September 2012 02:05:23 Derrick Edwards wrote: > >> Thanks again for looking into this. > >> > >> My main concern was the range of network performance that I was getting > >> > >> when the laptop was right in front of the access point. As you can see > >> > >> bandwith varied greatly. > > > > I don't know if it's related, but my RSSI and RATE jumps around quite a > > lot while transfering a large file. > > > > > > > > Output from loop doing "ifconfig wlan0 list sta" while transfering a big > > file. > > > > > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 86M 16.5 0 842 9440 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 43M 12.5 0 1063 14784 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 43M 15.5 0 1362 21088 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 86M 15.5 0 1627 27488 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 86M 13.5 0 2150 38976 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 86M 11.5 0 2289 42384 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 29M 24.5 0 3075 60016 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 86M 28.5 0 3369 1600 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 86M 14.0 0 3839 11744 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 29M 13.5 0 87 19936 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 58M 11.5 0 403 27440 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 58M 12.5 0 758 35200 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 58M 11.0 0 1054 42320 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 58M 23.5 0 1249 46512 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 29M 11.0 0 1381 49312 E AQHTR HTCAP WME > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > > > 00:0c:42:6c:58:29 1 128 58M 11.5 0 1584 54224 E AQHTR HTCAP WME > > > > > > > > System info = hybrid > > > > HW = gateworks ARM > > > > OS = FreeBSD-9 with ath code from current > > > > Wifi = RouterBOARD R52nM = AR9220 > > > > Distance = 8km > > > > > > > > B.t.w if I use the same HW with FreeBSD-9 in 11a mode, then RSSI does not > > jump around and I get about the same throuput as with N. > > > > > > > > I don't have any athstats output, still working on it. > > > > > > > > Johann r ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Performance of AR9287
I assume you've tweaked the ack, slot, rtsctstimeout? The 11n rate control code is a little more jumpy. I've fixed that in recent checkins. It's not optimal but now it's not as jumpy as before. Update to -HEAD, then use 'athratestats' on the peer MAC address. It's quite useful to see what's actually going on. :-) Adrian On 22 September 2012 01:20, Johann Hugo wrote: > On Saturday 22 September 2012 02:05:23 Derrick Edwards wrote: > >> Thanks again for looking into this. > >> My main concern was the range of network performance that I was getting > >> when the laptop was right in front of the access point. As you can see > >> bandwith varied greatly. > > > > I don't know if it's related, but my RSSI and RATE jumps around quite a lot > while transfering a large file. > > > > Output from loop doing "ifconfig wlan0 list sta" while transfering a big > file. > > > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 86M 16.5 0 842 9440 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 43M 12.5 0 1063 14784 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 43M 15.5 0 1362 21088 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 86M 15.5 0 1627 27488 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 86M 13.5 0 2150 38976 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 86M 11.5 0 2289 42384 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 29M 24.5 0 3075 60016 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 86M 28.5 0 3369 1600 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 86M 14.0 0 3839 11744 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 29M 13.5 0 87 19936 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 58M 11.5 0 403 27440 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 58M 12.5 0 758 35200 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 58M 11.0 0 1054 42320 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 58M 23.5 0 1249 46512 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 29M 11.0 0 1381 49312 E AQHTR HTCAP WME > > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > > 00:0c:42:6c:58:29 1 128 58M 11.5 0 1584 54224 E AQHTR HTCAP WME > > > > System info = hybrid > > HW = gateworks ARM > > OS = FreeBSD-9 with ath code from current > > Wifi = RouterBOARD R52nM = AR9220 > > Distance = 8km > > > > B.t.w if I use the same HW with FreeBSD-9 in 11a mode, then RSSI does not > jump around and I get about the same throuput as with N. > > > > I don't have any athstats output, still working on it. > > > > Johann ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Performance of AR9287
On Saturday 22 September 2012 02:05:23 Derrick Edwards wrote: > Thanks again for looking into this. > My main concern was the range of network performance that I was getting > when the laptop was right in front of the access point. As you can see > bandwith varied greatly. I don't know if it's related, but my RSSI and RATE jumps around quite a lot while transfering a large file. Output from loop doing "ifconfig wlan0 list sta" while transfering a big file. ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 86M 16.50842 9440 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 43M 12.50 1063 14784 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 43M 15.50 1362 21088 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 86M 15.50 1627 27488 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 86M 13.50 2150 38976 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 86M 11.50 2289 42384 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 29M 24.50 3075 60016 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 86M 28.50 3369 1600 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 86M 14.00 3839 11744 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 29M 13.50 87 19936 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 58M 11.50403 27440 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 58M 12.50758 35200 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 58M 11.00 1054 42320 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 58M 23.50 1249 46512 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 29M 11.00 1381 49312 EAQHTR HTCAP WME ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 00:0c:42:6c:58:291 128 58M 11.50 1584 54224 EAQHTR HTCAP WME System info = hybrid HW = gateworks ARM OS = FreeBSD-9 with ath code from current Wifi = RouterBOARD R52nM = AR9220 Distance = 8km B.t.w if I use the same HW with FreeBSD-9 in 11a mode, then RSSI does not jump around and I get about the same throuput as with N. I don't have any athstats output, still working on it. Johann ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Performance of AR9287
On 21 September 2012 17:30, Derrick Edwards wrote: > Wireless N, if any. Thanks for the info. AR5416 and AR9280. I suggest the AR9280 if you can. The later NICs (AR93xx, AR94xx, AR95xx) aren't supported at the moment. I have working code here but I can't release it just yet. Thanks, Adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Performance of AR9287
On Friday, September 21, 2012 08:24:27 PM Adrian Chadd wrote: > Hi, > > The AR9287 is a 2GHz only NIC. > > > > adrian Thanks alot. I did not know that. What NIC supports both 2GHz and 5GHz Wireless N, if any. Thanks for the info. ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Performance of AR9287
Hi, The AR9287 is a 2GHz only NIC. adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Performance of AR9287
On Friday, September 21, 2012 03:11:20 PM Adrian Chadd wrote: > Hiya, > > those results look fine, what's the problem exactly? > > Beforehand it was 2MBit/sec upload, now it's 50MBit/sec > upload/download, that looks within expectations and close to what > ath9k is getting. > > > > Adrian > > On 21 September 2012 04:01, Derrick Edwards wrote: > > On Friday, September 21, 2012 12:50:08 AM Adrian Chadd wrote: > >> Which iperf is upload and which is download? > >> > >> Can you run athstats during the transfer? > >> > >> Adrian > >> > >> On Sep 20, 2012 8:57 PM, "Derrick Edwards" wrote: > >> > Hi, > >> > > >> > I am utilizing an mini PCIE AR9287 mini PCI-E. It is not performing > >> > as expected thus far. I utilized iperf to test speed from laptops > >> > (both FreeBSD > >> > and Windows) to local default gateway. The results are show below with > >> > the first result being executed from the Windows Laptop and FreeBSD > >> > afterwards. Are these results to be expected? > >> > > >> > Derrick > >> > > >> > Windows > >> > > >> > Server listening on TCP port 5001 > >> > TCP window size: 64.0 KByte (default) > >> > > >> > [ 4] local 192.168.15.3 port 5001 connected with 192.168.15.153 port > >> > 58137 > >> > Client connecting to 192.168.15.153, TCP port 5001 > >> > TCP window size: 56.5 KByte (default) > >> > > >> > [ 6] local 192.168.15.3 port 49723 connected with 192.168.15.153 port > >> > 5001 Waiting for server threads to complete. Interrupt again to force > >> > quit. [ ID] Interval Transfer Bandwidth > >> > [ 4] 0.0-10.0 sec 14.3 MBytes 12.0 Mbits/sec > >> > [ 6] 0.0-10.0 sec 74.4 MBytes 62.4 Mbits/sec > >> > > >> > > >> > FreeBSD 10.0-CURRENT #0: Thu Sep 20 16:22:56 EDT 2012 > >> > > >> > Server listening on TCP port 5001 > >> > TCP window size: 64.0 KByte (default) > >> > > >> > [ 4] local 192.168.15.3 port 5001 connected with 192.168.15.238 port > >> > 44678 > >> > Client connecting to 192.168.15.238, TCP port 5001 > >> > TCP window size: 32.5 KByte (default) > >> > > >> > [ 6] local 192.168.15.3 port 40554 connected with 192.168.15.238 port > >> > 5001 Waiting for server threads to complete. Interrupt again to force > >> > quit. [ ID] Interval Transfer Bandwidth > >> > [ 4] 0.0-10.0 sec 74.4 MBytes 62.3 Mbits/sec > >> > [ 6] 0.0-10.1 sec 9.87 MBytes 8.21 Mbits/sec > >> > > >> > > >> > > >> > wlan0: flags=8843 metric 0 mtu > >> > 1500 > >> > > >> > ether 1c:65:9d:ab:18:6f > >> > inet 192.168.15.238 netmask 0xff00 broadcast > >> > 192.168.15.255 nd6 > >> > options=29 > >> > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng > >> > status: associated > >> > ssid datdude channel 1 (2412 MHz 11g ht/40+) bssid > >> > > >> > 10:bf:48:d9:1e:a0 > >> > > >> > regdomain FCC country US indoor ecm authmode WPA2/802.11i > >> > privacy > >> > > >> > ON > >> > > >> > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 7 scanvalid > >> > 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme > >> > burst roaming MANUAL > >> > > >> > ./athstats > >> > 495670 data frames received > >> > 605640 data frames transmit > >> > 1129 tx frames with an alternate rate > >> > 21720short on-chip tx retries > >> > 15941long on-chip tx retries > >> > 34 tx failed 'cuz too many retries > >> > 428 mib overflow interrupts > >> > 9tx linearized to cluster > >> > MCS4 current transmit rate > >> > 1watchdog timeouts > >> > 12 beacon miss interrupts > >> > 37 tx failed 'cuz destination filtered > >> > 21042rx failed 'cuz of bad CRC > >> > 7rx failed 'cuz decryption > >> > 5rx failed 'cuz of PHY err > >> > > >> > 5illegal service > >> > > >> > 354 periodic calibrations > >> > -0/+0TDMA slot adjust (usecs, smoothed) > >> > 58 rssi of last ack > >> > 48 avg recv rssi > >> > -96 rx noise floor > >> > 4phantom beacon misses > >> > 237 tx frames through raw api > >> > 303067 A-MPDU sub-frames received > >> > 136445 Half-GI frames received > >> > 321349 40MHz frames received > >> > 4339 CRC errors for non-last A-MPDU subframes > >> > 179 CRC errors for last subframe in an A-MPDU > >> > 128845 Frames transmitted with HT Protection > >> > 69601Number of frames retransmitted in software > >> > 556475 A-MPDU sub-frame TX attempt success > >> >
Re: Performance of AR9287
Hiya, those results look fine, what's the problem exactly? Beforehand it was 2MBit/sec upload, now it's 50MBit/sec upload/download, that looks within expectations and close to what ath9k is getting. Adrian On 21 September 2012 04:01, Derrick Edwards wrote: > On Friday, September 21, 2012 12:50:08 AM Adrian Chadd wrote: >> Which iperf is upload and which is download? >> >> Can you run athstats during the transfer? >> >> Adrian >> >> On Sep 20, 2012 8:57 PM, "Derrick Edwards" wrote: >> > Hi, >> > >> > I am utilizing an mini PCIE AR9287 mini PCI-E. It is not performing as >> > expected thus far. I utilized iperf to test speed from laptops (both >> > FreeBSD >> > and Windows) to local default gateway. The results are show below with >> > the first result being executed from the Windows Laptop and FreeBSD >> > afterwards. Are these results to be expected? >> > >> > Derrick >> > >> > Windows >> > >> > Server listening on TCP port 5001 >> > TCP window size: 64.0 KByte (default) >> > >> > [ 4] local 192.168.15.3 port 5001 connected with 192.168.15.153 port >> > 58137 >> > Client connecting to 192.168.15.153, TCP port 5001 >> > TCP window size: 56.5 KByte (default) >> > >> > [ 6] local 192.168.15.3 port 49723 connected with 192.168.15.153 port >> > 5001 Waiting for server threads to complete. Interrupt again to force >> > quit. [ ID] Interval Transfer Bandwidth >> > [ 4] 0.0-10.0 sec 14.3 MBytes 12.0 Mbits/sec >> > [ 6] 0.0-10.0 sec 74.4 MBytes 62.4 Mbits/sec >> > >> > >> > FreeBSD 10.0-CURRENT #0: Thu Sep 20 16:22:56 EDT 2012 >> > >> > Server listening on TCP port 5001 >> > TCP window size: 64.0 KByte (default) >> > >> > [ 4] local 192.168.15.3 port 5001 connected with 192.168.15.238 port >> > 44678 >> > Client connecting to 192.168.15.238, TCP port 5001 >> > TCP window size: 32.5 KByte (default) >> > >> > [ 6] local 192.168.15.3 port 40554 connected with 192.168.15.238 port >> > 5001 Waiting for server threads to complete. Interrupt again to force >> > quit. [ ID] Interval Transfer Bandwidth >> > [ 4] 0.0-10.0 sec 74.4 MBytes 62.3 Mbits/sec >> > [ 6] 0.0-10.1 sec 9.87 MBytes 8.21 Mbits/sec >> > >> > >> > >> > wlan0: flags=8843 metric 0 mtu >> > 1500 >> > >> > ether 1c:65:9d:ab:18:6f >> > inet 192.168.15.238 netmask 0xff00 broadcast 192.168.15.255 >> > nd6 options=29 >> > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng >> > status: associated >> > ssid datdude channel 1 (2412 MHz 11g ht/40+) bssid >> > >> > 10:bf:48:d9:1e:a0 >> > >> > regdomain FCC country US indoor ecm authmode WPA2/802.11i privacy >> > >> > ON >> > >> > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 7 scanvalid 60 >> > protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst >> > roaming MANUAL >> > >> > ./athstats >> > 495670 data frames received >> > 605640 data frames transmit >> > 1129 tx frames with an alternate rate >> > 21720short on-chip tx retries >> > 15941long on-chip tx retries >> > 34 tx failed 'cuz too many retries >> > 428 mib overflow interrupts >> > 9tx linearized to cluster >> > MCS4 current transmit rate >> > 1watchdog timeouts >> > 12 beacon miss interrupts >> > 37 tx failed 'cuz destination filtered >> > 21042rx failed 'cuz of bad CRC >> > 7rx failed 'cuz decryption >> > 5rx failed 'cuz of PHY err >> > >> > 5illegal service >> > >> > 354 periodic calibrations >> > -0/+0TDMA slot adjust (usecs, smoothed) >> > 58 rssi of last ack >> > 48 avg recv rssi >> > -96 rx noise floor >> > 4phantom beacon misses >> > 237 tx frames through raw api >> > 303067 A-MPDU sub-frames received >> > 136445 Half-GI frames received >> > 321349 40MHz frames received >> > 4339 CRC errors for non-last A-MPDU subframes >> > 179 CRC errors for last subframe in an A-MPDU >> > 128845 Frames transmitted with HT Protection >> > 69601Number of frames retransmitted in software >> > 556475 A-MPDU sub-frame TX attempt success >> > 69579A-MPDU sub-frame TX attempt failures >> > 6A-MPDU TX frame failures >> > 2first step level >> > 1OFDM weak signal detect >> > 140 ANI increased noise immunity >> > 140 ANI decrease noise immunity >> > 1ANI increased spur immunity >> > 1ANI decrease spur immunity >> >
Re: Performance of AR9287
On Friday, September 21, 2012 12:50:08 AM Adrian Chadd wrote: > Which iperf is upload and which is download? > > Can you run athstats during the transfer? > > Adrian > > On Sep 20, 2012 8:57 PM, "Derrick Edwards" wrote: > > Hi, > > > > I am utilizing an mini PCIE AR9287 mini PCI-E. It is not performing as > > expected thus far. I utilized iperf to test speed from laptops (both > > FreeBSD > > and Windows) to local default gateway. The results are show below with > > the first result being executed from the Windows Laptop and FreeBSD > > afterwards. Are these results to be expected? > > > > Derrick > > > > Windows > > > > Server listening on TCP port 5001 > > TCP window size: 64.0 KByte (default) > > > > [ 4] local 192.168.15.3 port 5001 connected with 192.168.15.153 port > > 58137 > > Client connecting to 192.168.15.153, TCP port 5001 > > TCP window size: 56.5 KByte (default) > > > > [ 6] local 192.168.15.3 port 49723 connected with 192.168.15.153 port > > 5001 Waiting for server threads to complete. Interrupt again to force > > quit. [ ID] Interval Transfer Bandwidth > > [ 4] 0.0-10.0 sec 14.3 MBytes 12.0 Mbits/sec > > [ 6] 0.0-10.0 sec 74.4 MBytes 62.4 Mbits/sec > > > > > > FreeBSD 10.0-CURRENT #0: Thu Sep 20 16:22:56 EDT 2012 > > > > Server listening on TCP port 5001 > > TCP window size: 64.0 KByte (default) > > > > [ 4] local 192.168.15.3 port 5001 connected with 192.168.15.238 port > > 44678 > > Client connecting to 192.168.15.238, TCP port 5001 > > TCP window size: 32.5 KByte (default) > > > > [ 6] local 192.168.15.3 port 40554 connected with 192.168.15.238 port > > 5001 Waiting for server threads to complete. Interrupt again to force > > quit. [ ID] Interval Transfer Bandwidth > > [ 4] 0.0-10.0 sec 74.4 MBytes 62.3 Mbits/sec > > [ 6] 0.0-10.1 sec 9.87 MBytes 8.21 Mbits/sec > > > > > > > > wlan0: flags=8843 metric 0 mtu > > 1500 > > > > ether 1c:65:9d:ab:18:6f > > inet 192.168.15.238 netmask 0xff00 broadcast 192.168.15.255 > > nd6 options=29 > > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng > > status: associated > > ssid datdude channel 1 (2412 MHz 11g ht/40+) bssid > > > > 10:bf:48:d9:1e:a0 > > > > regdomain FCC country US indoor ecm authmode WPA2/802.11i privacy > > > > ON > > > > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 7 scanvalid 60 > > protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst > > roaming MANUAL > > > > ./athstats > > 495670 data frames received > > 605640 data frames transmit > > 1129 tx frames with an alternate rate > > 21720short on-chip tx retries > > 15941long on-chip tx retries > > 34 tx failed 'cuz too many retries > > 428 mib overflow interrupts > > 9tx linearized to cluster > > MCS4 current transmit rate > > 1watchdog timeouts > > 12 beacon miss interrupts > > 37 tx failed 'cuz destination filtered > > 21042rx failed 'cuz of bad CRC > > 7rx failed 'cuz decryption > > 5rx failed 'cuz of PHY err > > > > 5illegal service > > > > 354 periodic calibrations > > -0/+0TDMA slot adjust (usecs, smoothed) > > 58 rssi of last ack > > 48 avg recv rssi > > -96 rx noise floor > > 4phantom beacon misses > > 237 tx frames through raw api > > 303067 A-MPDU sub-frames received > > 136445 Half-GI frames received > > 321349 40MHz frames received > > 4339 CRC errors for non-last A-MPDU subframes > > 179 CRC errors for last subframe in an A-MPDU > > 128845 Frames transmitted with HT Protection > > 69601Number of frames retransmitted in software > > 556475 A-MPDU sub-frame TX attempt success > > 69579A-MPDU sub-frame TX attempt failures > > 6A-MPDU TX frame failures > > 2first step level > > 1OFDM weak signal detect > > 140 ANI increased noise immunity > > 140 ANI decrease noise immunity > > 1ANI increased spur immunity > > 1ANI decrease spur immunity > > 127 ANI disabled OFDM weak signal detect > > 127 ANI disabled CCK weak signal threshold > > 2ANI increased first step level > > 251877 cumulative OFDM phy error count > > 348293 cumulative CCK phy error count > > 431 ANI forced listen time to zero > > 15583missing ACK's > > 23402RTS without C
Re: Performance of AR9287
Which iperf is upload and which is download? Can you run athstats during the transfer? Adrian On Sep 20, 2012 8:57 PM, "Derrick Edwards" wrote: > Hi, > I am utilizing an mini PCIE AR9287 mini PCI-E. It is not performing as > expected thus far. I utilized iperf to test speed from laptops (both > FreeBSD > and Windows) to local default gateway. The results are show below with the > first result being executed from the Windows Laptop and FreeBSD afterwards. > Are these results to be expected? > > Derrick > > Windows > > Server listening on TCP port 5001 > TCP window size: 64.0 KByte (default) > > [ 4] local 192.168.15.3 port 5001 connected with 192.168.15.153 port 58137 > > Client connecting to 192.168.15.153, TCP port 5001 > TCP window size: 56.5 KByte (default) > > [ 6] local 192.168.15.3 port 49723 connected with 192.168.15.153 port 5001 > Waiting for server threads to complete. Interrupt again to force quit. > [ ID] Interval Transfer Bandwidth > [ 4] 0.0-10.0 sec 14.3 MBytes 12.0 Mbits/sec > [ 6] 0.0-10.0 sec 74.4 MBytes 62.4 Mbits/sec > > > FreeBSD 10.0-CURRENT #0: Thu Sep 20 16:22:56 EDT 2012 > > Server listening on TCP port 5001 > TCP window size: 64.0 KByte (default) > > [ 4] local 192.168.15.3 port 5001 connected with 192.168.15.238 port 44678 > > Client connecting to 192.168.15.238, TCP port 5001 > TCP window size: 32.5 KByte (default) > > [ 6] local 192.168.15.3 port 40554 connected with 192.168.15.238 port 5001 > Waiting for server threads to complete. Interrupt again to force quit. > [ ID] Interval Transfer Bandwidth > [ 4] 0.0-10.0 sec 74.4 MBytes 62.3 Mbits/sec > [ 6] 0.0-10.1 sec 9.87 MBytes 8.21 Mbits/sec > > > > wlan0: flags=8843 metric 0 mtu 1500 > ether 1c:65:9d:ab:18:6f > inet 192.168.15.238 netmask 0xff00 broadcast 192.168.15.255 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng > status: associated > ssid datdude channel 1 (2412 MHz 11g ht/40+) bssid > 10:bf:48:d9:1e:a0 > regdomain FCC country US indoor ecm authmode WPA2/802.11i privacy > ON > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 7 scanvalid 60 > protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst > roaming MANUAL > > ./athstats > 495670 data frames received > 605640 data frames transmit > 1129 tx frames with an alternate rate > 21720short on-chip tx retries > 15941long on-chip tx retries > 34 tx failed 'cuz too many retries > 428 mib overflow interrupts > 9tx linearized to cluster > MCS4 current transmit rate > 1watchdog timeouts > 12 beacon miss interrupts > 37 tx failed 'cuz destination filtered > 21042rx failed 'cuz of bad CRC > 7rx failed 'cuz decryption > 5rx failed 'cuz of PHY err > 5illegal service > 354 periodic calibrations > -0/+0TDMA slot adjust (usecs, smoothed) > 58 rssi of last ack > 48 avg recv rssi > -96 rx noise floor > 4phantom beacon misses > 237 tx frames through raw api > 303067 A-MPDU sub-frames received > 136445 Half-GI frames received > 321349 40MHz frames received > 4339 CRC errors for non-last A-MPDU subframes > 179 CRC errors for last subframe in an A-MPDU > 128845 Frames transmitted with HT Protection > 69601Number of frames retransmitted in software > 556475 A-MPDU sub-frame TX attempt success > 69579A-MPDU sub-frame TX attempt failures > 6A-MPDU TX frame failures > 2first step level > 1OFDM weak signal detect > 140 ANI increased noise immunity > 140 ANI decrease noise immunity > 1ANI increased spur immunity > 1ANI decrease spur immunity > 127 ANI disabled OFDM weak signal detect > 127 ANI disabled CCK weak signal threshold > 2ANI increased first step level > 251877 cumulative OFDM phy error count > 348293 cumulative CCK phy error count > 431 ANI forced listen time to zero > 15583missing ACK's > 23402RTS without CTS > 94745successful RTS > 77637bad FCS > 102509 beacons received > 66 average rssi (beacons only) > 59 average rssi (all rx'd frames) > 60 average rssi (ACKs only) > Antenna profile: > [0] tx87529 rx 100 > [1] tx0 rx 495570 > > > > ath0@pci0:2:0:0:class=0x028000 c
