wpa_supplicant: secured mesh and WiLink8 issue

[Machani, Yaniv]

Hi Yegor, 
To establish a baseline here, 
Can you try using the officially supported packages by TI (Version R8.7) ?
See release notes here : http://software-dl.ti.com/ecs/WiLink8/R8_7/exports/release_notes_R8_7.html
It was validated to work with open and secured modes, based on Kernel 4.4.8 and hostap 2.5+
Related commits:
Hostap : http://git.ti.com/wilink8-wlan/hostap/commit/2f81a831e29a4d44d6abbac34e3280e8471f61ef
Linux Kernel : http://git.ti.com/wilink8-wlan/wl18xx/commit/13c25bca8d5229c8d5cf5776a13647b020e29588
The Firmware version you are using is supporting secured mesh, so no issues there.

You can also have a look in our build guides http://processors.wiki.ti.com/index.php/WL18xx_System_Build_Scripts


Regards,
Yaniv

On Sat, Nov 05, 2016 at 17:38:29, Bob Copeland wrote:
> Maxim; Hahn, Maital; Machani, Yaniv
> Subject: Re: wpa_supplicant: secured mesh and WiLink8 issue
> 
> On Fri, Nov 04, 2016 at 01:47:07PM +0100, Yegor Yefremov wrote:
> > > of thing if the hardware doesn't support the necessary encryption 
> > > primitives for mesh.
> >
> > this the wl18xx driver for TI WiLink8 hardware:
> >
> > [    9.032606] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
> > [    9.262579] wlcore: loaded
> > [   17.962749] wlcore: PHY firmware version: Rev 8.2.0.0.236
> > [   18.036955] wlcore: firmware booted (Rev 8.9.0.0.69)
>

 
> Ok, my advice would be to capture the HWMP frames both over the air 
> with a third-party monitor and also on one of the nodes.  If HWMP PREQ 
> or PREP doesn't show up over the air, then there's something wrong on 
> the sender side; if it doesn't show up on the target then it's probably filtered at the receiver (e.g.
> possibly decrypt / verify failed, broadcast frames are filtered, etc).  
> If it does show up on both nodes but, say, PREQ is not being replied 
> to, then perhaps kernel is dropping it for some reason and that would take more debugging.
> 
> At this point though it feels like more of a driver/kernel issue than 
> a wpa_supplicant problem.  You can verify your wpa_s setup with ath9k 
> (/_htc) or even with hwsim, both should work.
> 
> --
> Bob Copeland %% http://bobcopeland.com/