Mesh on ath10k drops all packets

[Jeroen Roovers]

On 22 January 2016 at 13:51, Bob Copeland <me at bobcopeland.com> wrote:
> On Fri, Jan 22, 2016 at 12:01:36PM +0100, Jeroen Roovers wrote:
>> Maybe related?
>
> Could be.

[..]

> What happens with non-secure mesh, i.e.:
>
> user_mpm=1
> network={
>     mode=5
>     ssid="_"
>     frequency=2412
>     key_mgmt=NONE
> }

That works fine!

> You don't really need to specify proto, pairwise, and group, by the way.

I seem to recall having to do this for an older version of wpa_supplicant.

>> > On 22 January 2016 at 11:38, Jeroen Roovers <jeroen.roovers at airfi.aero> wrote:
>> >> Jan 22 11:34:21 wim kernel: wlan0: TBTT : max clockdrift=0; too small to adjust
>> >> Jan 22 11:34:22 wim kernel: wlan0: STA 40:e2:30:cb:9a:11 : offset was
>> >> invalid, t_offset=1712128384
>> >> Jan 22 11:34:22 wim kernel: wlan0: TBTT : max clockdrift=0; too small to adjust
>> >> Jan 22 11:34:23 wim kernel: wlan0: STA 40:e2:30:cb:9a:11 : is adjusting TBTT
>> >> Jan 22 11:34:23 wim kernel: wlan0: TBTT : max clockdrift=0; too small to adjust
>> >> Jan 22 11:34:24 wim kernel: wlan0: STA 40:e2:30:cb:9a:11 : offset was
>> >> invalid, t_offset=1714176384
>
> All of this is just mesh sync debugging, you actually don't really need
> mesh sync unless you are doing power save, collision avoidance, or
> controlled channel access, none of which are fully implemented in the
> kernel.

Yes, that seems to be because I turned on lots of debug output in the
ath10 driver.

Regards,
     jer