R: R: Link can't get estabilished over RB911AC boards

Alessandro Bolletta alessandro at mediaspot.net
Mon Sep 21 16:20:39 PDT 2015


Ok Ben, thanks for you infos.

Just for curiosity: do you think that ath10k could be better in performances than official QCA reference drivers (the same used in proprietary distros as RouterOS, for example)?

Alessandro

-----Messaggio originale-----
Da: Ben Greear [mailto:greearb at candelatech.com] 
Inviato: martedì 22 settembre 2015 01.19
A: Alessandro Bolletta <alessandro at mediaspot.net>; ath10k at lists.infradead.org
Oggetto: Re: R: Link can't get estabilished over RB911AC boards

On 09/21/2015 03:18 PM, Alessandro Bolletta wrote:
> Great!
>
> Ben, could you tell me how to compile CT kernel, for example the 4.2 version, as part of OpenWRT buildroot?
>
> Also, what do you suggest for stability reasons? CT 4.0 or 4.2?

4.0 is most stable currently, though the last few days I've been committing a lot of barely tested code.  Will test this better shortly.

And, sorry, but I don't have time right now to help with making this work with OpenWrt.  At the least, it is liable to not be trivial.  Search the list for 'CT' + 'OpenWRT' an you may find some help...others have posted patch-sets for OpenWRT that includes at least many of my patches.


Thanks,
Ben

>
> Thanks,
> Alessandro
>
> -----Messaggio originale-----
> 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:
>> Hi,
>>
>> 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.
>
> http://dmz2.candelatech.com/?p=linux-4.0.dev.y/.git;a=commit;h=abd3ee5
> c4d297e56b854864624152f5704c5df20
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>
>
>
>


--
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com






More information about the ath10k mailing list