Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 9 Sep 2011 20:08:41 +0800
From:      Adrian Chadd <adrian@freebsd.org>
To:        Lev Serebryakov <lev@serebryakov.spb.ru>
Cc:        freebsd-wireless@freebsd.org
Subject:   Re: AP performance (again): txpower regulation
Message-ID:  <CAJ-VmonUioh4g3NScinYDU6gEFWDLeGKUYQfRyNoWr5%2BfjQeTw@mail.gmail.com>
In-Reply-To: <CAJ-VmomQQGgSf=R8A1bvF9s_FqWBaCCzwFjG5eaoWAOhjHKkiw@mail.gmail.com>
References:  <663133681.20110907193747@serebryakov.spb.ru> <CAJ-Vmonai4LzwanLw7i5d-NyjN2b6GqfttjkdcROvOuEcuzEAw@mail.gmail.com> <437702009.20110907235248@serebryakov.spb.ru> <CAJ-Vmo=R-a%2BqhDLWj1n%2BBj70Pmg4WSL6bVZ6jwCUmNq=v7EBBw@mail.gmail.com> <426917282.20110908125907@serebryakov.spb.ru> <CAAUsrB5Qtokpcz-koUfYWCHrsnUUErQSAYHrXrW2F0Uvp3RzSA@mail.gmail.com> <4610390305.20110908154130@serebryakov.spb.ru> <CAAUsrB6LJ%2BmuTvaqHCySh6e9dMjzshohYFE4PQ3KTezZMZS2JA@mail.gmail.com> <1705262661.20110908180850@serebryakov.spb.ru> <CAAUsrB7CFu096x%2BKKWa=8O_VeSHOK10LuwJ2rWq6r8EidUrL=Q@mail.gmail.com> <CAJ-VmokvXfUAZpxDgv5gLrRdLYn3YwTXAOb7QiTyUg8K5yKLHg@mail.gmail.com> <458771414.20110908183656@serebryakov.spb.ru> <CAJ-Vmom_ZHKbqt%2BQgmdq_oPU-SugbrJ3LNS=g-cpcQ7KExusUw@mail.gmail.com> <4910491962.20110908185213@serebryakov.spb.ru> <CAJ-Vmo==J_9ZhnSciVKNaEaMhM4oeM9fr4yjzPev_MW3g9DALg@mail.gmail.com> <1273865639.20110908191303@serebryakov.spb.ru> <1607911768.20110909113824@serebryakov.spb.ru> <1853154884.20110909145338@serebryakov.spb.ru> <CAJ-VmokAvtKTUGo5zBS3ry0nRH=P%2B1TNB2n-9dKK%2BSWn6FdJ2A@mail.gmail.com> <140679489.20110909154614@serebryakov.spb.ru> <CAJ-VmomQQGgSf=R8A1bvF9s_FqWBaCCzwFjG5eaoWAOhjHKkiw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
.. I forgot to cc- the list.

Also to clarify:

* short retries are "I sent an RTS but didn't hear a CTS."
* long retries are "I sent the frame but didn't hear an ACK."

Since the default athstats doesn't spit out the ofdm and cck errors, try this:

athstats -o input,output,altrate,short,long,xretry,crcerr,crypt,phyerr,rssi,ofdm,cck,rate
1



Adrian

On 9 September 2011 20:06, Adrian Chadd <adrian@freebsd.org> wrote:
> Right.
>
> xretry means "exceeded retries". Ie, all the chip retries failed.
>
> On the TX side of things - look at how high your long retry count is.
> That means the chip TXed the frame and it didn't hear an ACK back.
>
> Let's focus on RX for now, as TX may just be a little screwy.
>
> Try a 20mbit UDP test stream from the client -> hostap -> server:
>
> server:
>
> iperf -su -i 1
>
> iperf -c <server ip> -ub 20m -t 30
>
> Then see what the receive rate is like.
>
>
>
> adrian
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonUioh4g3NScinYDU6gEFWDLeGKUYQfRyNoWr5%2BfjQeTw>