Re: Mesh on ath10k drops all packets

[Bob Copeland <me@bobcopeland.com>]

On Fri, Jan 22, 2016 at 12:01:36PM +0100, Jeroen Roovers wrote:
> Maybe related?

Could be.

> On 22 January 2016 at 11:55, Jeroen Roovers <jeroen.roovers@airfi.aero> wrote:
> > wpa_supplicant config looks like this:
> >
> > user_mpm=1
> > update_config=1
> >
> > network={
> >         mode=5
> >         ssid="_"
> >         frequency=2412
> >         proto=RSN
> >         key_mgmt=SAE
> >         pairwise=CCMP
> >         group=CCMP
> >         psk="..."
> > }

What happens with non-secure mesh, i.e.:

user_mpm=1
network={
    mode=5
    ssid="_"
    frequency=2412
    key_mgmt=NONE
}

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

> > On 22 January 2016 at 11:38, Jeroen Roovers <jeroen.roovers@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.

-- 
Bob Copeland %% http://bobcopeland.com/

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k