wpa_supplicant, SAE secured MESH on RT5370 doesn't PING after peer connection is established

Greg Gigon greg.gigon at gmail.com
Sun Nov 20 03:24:59 PST 2016

I’m using Raspbian, which is based of Debian 8 (Jessie), but compiled for ARM processor.
I don’t think Raspbian does backports, unfortunately. 
I could possibly try to recompile the single kernel module myself.
Would you suggest anything else?

> On 19 Nov 2016, at 15:22, Jouni Malinen <j at w1.fi> wrote:
> On Sat, Nov 19, 2016 at 12:19:24PM +0000, Greg Gigon wrote:
>> I’ve been trying wpa_supplicant on Raspnerry PI running latest Raspbian. Open mesh network works fine, however SEA key management doesn’t. 
>> By doesn’t I mean, it’s not resolving MAC via ARP and not being able to PING. 
>> I’m testing this on 2 nodes. Running the same Wireless chipset. 
>> Bellow is a lot of information about my env. Same setup is pretty much on both RasPI, the only difference is the IP address. 
>> pi at raspberrypi3bare:~ $ uname -a
>> Linux raspberrypi3bare 4.4.21-v7+ #911 SMP Thu Sep 15 14:22:38 BST 2016 armv7l GNU/Linux
> Are you using the WLAN driver implementation from that kernel version or
> updated version from Backports? If this is what comes with Linux 4.4,
> there is a known issue in secure mesh and you would need to update the
> kernel (or at least mac80211 using Backports) to make this work.
>> pi at raspberrypi3bare:~ $ wpa_supplicant -v
>> wpa_supplicant v2.6
> wpa_supplicant v2.6 has all the known mesh related issues fixed, but
> this depends on the kernel (mac80211) having related issues addressed.
> -- 
> Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list