|Summary:||[PATCH] Add an option for wpa_supplicant to create the control interface socket|
|Product:||Base System||Reporter:||Yuri Victorovich <yuri>|
|Component:||conf||Assignee:||freebsd-bugs (Nobody) <bugs>|
|Severity:||Affects Only Me||CC:||adrian, pi|
Description Yuri Victorovich 2016-07-19 05:39:31 UTC
Created attachment 172695 [details] patch This patch added the option -C <ctrl> for wpa_supplicant to always create the control interface. Users on the mobile devices often need to connect to various WiFi networks. This usually requires the access to wpa_supplicant control interface. The control interface socket is only readable by root and wheel: > # ls -l /var/run/wpa_supplicant/wlan0 > srwxrwx--- 1 root wheel 0 Jul 18 22:19 /var/run/wpa_supplicant/wlan0 One example of the program using the control interface is wpa_supplicant's own UI: net/wpa_gui port.
Comment 1 Adrian Chadd 2016-08-12 20:23:12 UTC
hi, this is something that can be put in wpa_supplicant.conf . Although, I don't knwo if you can say "this current interface" in that file.. I'll go look at the patch. :) Thanks!
Comment 2 Yuri Victorovich 2016-08-12 20:52:00 UTC
I think /var/run/wpa_supplicant socket path should be pre-set in rc scripts because this path is already pre-set in wpa_gui, and it won't make sense to have user remember this bit of information and do this manually every time. Also most rc scripts set socket locations for various other ports that use UNIX sockets.