Hi,
Based on my observations, there's a regression from backport 3.14-1 to 3.15-rc1-1 for WPA2 encrypted access point managed with hostapd. It might be related.
Basically with backport 3.10.17-1, 3.12-1 and 3.14-1 I can spawn an soft access point encrypted with WPA2 and connect to it but not with 3.15-rc1-1.
On July 14, 2014 at 10:13 AM Bob Copeland <[email protected]> wrote:
On Mon, Jul 14, 2014 at 02:01:45PM +0000, Lukas Göstl wrote:
> Hi,
>
> i succesfully build up a secure Mesh Network with AuthSAE with the
> Kernel-Version 3.10. Now I installed the Kernel-Version 3.15 on my
> device. I noticed that the secure Mode is only working when both
> devices have the same kernel-version. The peers with different
> Kernel-Versions are not seeing each other and I get no output of "iw
> dev mesh0 station dump". The open80211 without AuthSAE is working
> perfectly between different Kernel-Versions.
>
> So my question is why the secure Mesh Network with AuthSAE only works
> with devices which have the same kernel-version and what can I do to
> fix it?
Hmm, I'm not aware of the actual problem -- but that description might
explain the issues I was having with wpa_supplicant over the weekend.
As the first step of authentication, the userspace daemons register with
the kernel to get notification when any new peers are available. It's
possible that the checks for which peers are acceptable changed somehow
between the kernel versions and so the notifications aren't delivered.
The best bet is to try to bisect it: try 3.13 on one device, then either
3.12 or 3.14, to try to narrow down when the change/regression was
introduced.
--
Bob Copeland %% www.bobcopeland.com
_______________________________________________
Devel mailing list
[email protected]
http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
_______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
