Hi,
We have observed a problem where, under certain conditions, the ath10k firmware
will acknowledge frames but not send them up to the driver.
Frames are sent by a mesh access point (MAP1) to a second mesh AP (MAP2) at MCS
9/NSS-3, which at that distance is probably marginal. Since frames ge
-a
On 7 February 2018 at 14:15, Javier Cardona wrote:
> Hi,
>
> We have observed a problem where, under certain conditions, the ath10k
firmware will acknowledge frames but not send them up to the driver.
> Frames are sent by a mesh access point (MAP1) to
0x
MAC-FILTER-ADDR-U16 0x
We would probably be still trying to solve this if Ben Greear did not point us
in the right direction.
Cheers,
Javier
On 2/7/18, 2:15 PM, "Javier Cardona" wrote:
Hi,
We have observed a problem where, under
Thomas,
On 3/13/18, 5:53 PM, "Thomas Pedersen" wrote:
Javier,
On Tue, Mar 13, 2018 at 4:42 PM, Javier Cardona wrote:
> Hi,
>
> We have resolved this issue. I'm sharing the details in case that might
help others.
>
> The
Hi Adrian,
On 3/13/18, 5:21 PM, "Adrian Chadd" wrote:
HI,
What were the mac addresses? Why were they so dissimilar?
The addresses on the pre-cal files were 12:34:56:78:90:12
We changed them to manufacturer assigned macs.
Thanks!
Javier
-adrian
___
