On 5/8/2018 5:05 PM, Denis Kenzior wrote:
Hi Arend,
Sure. I guess we all have been there kicking of wpa_s and discovering
there is already one running in the background. I am just a bit
squeamish to change the behavior like this. Hmmmm. Is wpa_s already
using SOCKET_OWNER. If so, I might create a patch to opt-out for that
so people can knowingly choose chaos ;-)
wpa_s is using SOCKET_OWNER these days. However, with the introduction
of Control Port over NL80211, just getting rid of SOCKET_OWNER might not
be that easy.
I have a regression test script employing py80211 which listens for
connect event. Right now I am using an older wpa_s, but the above will
screw it up.
If I recall correctly the mlme notification needed to be unicast,
because multicast was not 100% reliable, right? Would it be acceptable
to send unicast to the socket owner and still do the multicast or are we
already doing that? If not, that would fix my imminent issue.
Regards,
Arend
