On Sat, May 23, 2020 at 9:57 AM Stefan Sperling <s...@stsp.name> wrote:
> On Fri, May 22, 2020 at 05:12:23PM +0200, stolen data wrote: > > On Thu, May 21, 2020 at 9:11 AM Stefan Sperling <s...@stsp.name> wrote: > > > > > On Thu, May 21, 2020 at 01:04:36AM +0200, stolen data wrote: > > > > > > ... > > > > > > > > > > You can try MCS1, MCS2, ..., all the way up to MCS15. > > > > > > > > Unfortunately no change. Some are unusable but none of them offer a > > > > visible improvement. > > > > > > Oh. So they all have the exact same result? > > > > > > > None of MCS0-15 can reach beyond 1200 Kbit/s and some are exceptionally > > unstable; 5-7 and 13-15 (with emphasis on 7 and 15) are so shaky that > > the speed drops below 50 Kbit/s and sometimes cause the entire link to > > choke and drop out. Across the range it seems to be best at 0/8 and > > degrade towards 7/15. I can't see any difference between the lower and > > upper range, and autoselect overall seems to work out better over time > > despite still being very jumpy. > > > > On AR9280 OpenBSD athn(4) will easily do 10 Mbit/s under good conditions, > if not more. Which is fairly bad given what the hardware is capable of. > But not nearly as bad as what you're seeing. > > It really sounds like a case where someone with AR9287 hardware in front > of them will need to debug the driver. > > Recording packet captures with another device in monitor mode might be > worth doing just to see if it sheds some light on the problem. > Would you be able to instruct me in how to capture traffic for this particular scenario? Assuming a packet dump from my end would be of any help that is. If none of the developers have an AR9287 available I will gladly lend this card for that purpose, granted that whoever receives it is OK with returning it afterwards. I'll pay shipping both ways of course.
