R: Link can't get estabilished over RB911AC boards
alessandro at mediaspot.net
Tue Sep 22 14:09:23 PDT 2015
Just one more information Ben: this patch introduces ack timing in ath10k, but in order to set it, has it to be triggered manually in debugfs or is it UCI (openwrt) able to set it automatically by his configuration process?
Also, there's a little thing that i'm not understanding: is it the firmware that controls ack timings or is it related to ath10k?
Thanks in advance and please be patient with me, I'm not an expert, but i'd like to be :)
Da: Ben Greear [mailto:greearb at candelatech.com]
Inviato: lunedì 21 settembre 2015 22.37
A: Alessandro Bolletta <alessandro at mediaspot.net>; ath10k at lists.infradead.org
Oggetto: Re: Link can't get estabilished over RB911AC boards
On 09/21/2015 12:57 PM, Alessandro Bolletta wrote:
> I have two Mikrotik RB911AC boards (radio based on QCA9882) in which I injected OpenWRT 15.05 and ath10k.
> I managed to get them connected in AP/STA configuration in a very short (2 meters) distance, but when I try to connect them on 5 kilometers, even if I set the distance parameter on OpenWRT's UCI config files properly, it tries to connect but after 3 retries, it declares unauthenticated.
> No problem with the same firmware on ath9k, for example.
> Signal is stable at -62 dbm, I also tried to change channels and push tx power, but nothing helped to do the trick.
> Also tried with every firmware combination (10.2.4, CT firmware, 999.999.0.636, 10.1.467.2-1), without success.
> Is there anybody who can tell me why? Could it be due to the kernel version (i'm running on 3.18.21)?
You probably need to adjust ack timings. I have some un-tested firmware support for this in the CT firmware, but I haven't fully wired it up to the driver.
Someone with a bit of time and skill could add this to the ath10k driver if they wanted to. This commit has some details.
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc http://www.candelatech.com
More information about the ath10k