wpa_supplicant control interface

[Jörg Krause]

I am using the wpa_supplicant control interface (wpa_ctrl) for an native 
nodejs addon implementation.

The documentation for wpa_ctrl_recv 
(http://w1.fi/wpa_supplicant/devel/wpa__ctrl_8h.html) says that it will 
block if no messages are available.

Looking at the source code of wpa_ctrl.c shows this is not true for 
linux sockets. In wpa_ctrl_open() the unix socket is set as non-blocking 
and that's why wpa_ctrl_receive(), which calls recv(), returns 
immediatly with -1.

Maybe the documentation needs an update since there was a patch in 2012 
which introduced the non-blocking sockets?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.shmoo.com/pipermail/hostap/attachments/20141001/c4787884/attachment.htm>