wpa_supplicant: secured mesh and WiLink8 issue

Yegor Yefremov yegorslists at googlemail.com
Fri Nov 4 04:33:38 PDT 2016

On Fri, Nov 4, 2016 at 12:10 PM, Bob Copeland <me at bobcopeland.com> wrote:
> On Fri, Nov 04, 2016 at 11:13:12AM +0100, Jeroen Roovers wrote:
>> On 4 November 2016 at 09:48, Yegor Yefremov <yegorslists at googlemail.com> wrote:
>> > I get a connection:
>> >
>> > mesh: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed
>> > [id=0 id_str=]
>> > mesh: MESH-GROUP-STARTED ssid="mymesh" id=0
>> > mesh: new peer notification for 54:4a:16:18:ef:50
>> > mesh: mesh plink with 54:4a:16:18:ef:50 established
>> > mesh: MESH-PEER-CONNECTED 54:4a:16:18:ef:50
>> >
>> > But network layer is not working, i.e. ARP resolution etc. What's the problem?
>> Sounds familiar. Can you check if broadcast packets are received
>> properly whereas unicast packets are not?
>> Which version of wpa_supplicant is that?
> I wrote up an explanation of a possible cause and solution here:
> https://bobcopeland.com/blog/2016/10/encrypted-mesh-psa/

wpa_supplicant is 2.7-devel i.e. git master

tcpdump shows nothing either unicast or broadcasts

So I both new kernel and newest wpa_supplicant. I've also added
ieee80211w=2, but no change.

Do I still need authsae daemon? If I use authsar-nl80211 I get
segmantation fault after

 sae_debug(MESHD_DEBUG, "new peer candidate (seq num=%d)\n",


More information about the Hostap mailing list