Hi,
On linux, the wpa_supplicant.config has some options, including remembering multiple wifi networks and the selection of the 'best' one based on policy and signal strength.
On genode, this file is generated by the genode code inside wifi_drv containing only one entry depending on the "selected_accesspoint" config node.
So if I may ask, is it possible to write the file yourself and use all features of wpa_supplicant on genode, or has it been stripped of all (or parts of) the functionality and should I use selected_accesspoint instead?
Hello Boris,
* Boris Mulder <boris.mulder@...434...> [2017-10-30 09:57:11 +0100]:
On genode, this file is generated by the genode code inside wifi_drv containing only one entry depending on the "selected_accesspoint" config node.
Truth be told we did not test if it works to add multiple networks and to let wpa_supplicant choose the best one. In theory it should work as intended; we did not remove any mechanisms providing this functionality.
So if I may ask, is it possible to write the file yourself and use all features of wpa_supplicant on genode, or has it been stripped of all (or parts of) the functionality and should I use selected_accesspoint instead?
No, the existence of this file (wpa_supplicant.conf) is merely an implementation detail and should be of no concern to the user (and it is regrettable that the user has to deal with it at all). Using the 'wlan_configuration' config is the canonical way to configure the wifi_drv component.
That being said, the decision to use the conf file under the hood to configure the supplicant was made because when doing the initial port it was the least time consuming way to get it up and running. Ideally, it would be better to enable the control interface but for the time being, the conf file approach seems to be good enough.
Regards, Josef
Ok, in that case I will just try it out. I'll let you know my findings once I have tested it for the functionality I currently need myself.
Another question: When the wifi_drv connects to a network, it seems to stop searching for other networks and the wlan_accesspoints ROM is left untouched. It remains populated with stale entries (or no entries if the connection succeeded immediately upon startup). This should be easily verifiable by setting the report_rom to verbose in the wifi run script.
Is this intended or is it a bug, and how can I keep it generating those reports?
* Boris Mulder <boris.mulder@...434...> [2017-10-30 17:11:36 +0100]:
Another question: When the wifi_drv connects to a network, it seems to stop searching for other networks and the wlan_accesspoints ROM is left untouched. It remains populated with stale entries (or no entries if the connection succeeded immediately upon startup). This should be easily verifiable by setting the report_rom to verbose in the wifi run script.
Is this intended or is it a bug, and how can I keep it generating those reports?
To quote 'repos/dde_linux/README':
Per default, the driver scans for available networks only when not connected. This can be changed with the 'connected_scan_interval' config attribute, which specifies the interval for connected scans in seconds, e.g. […]
The driver is supposed to do that if you set the attribute. If it does not, please file a bug report.
Regards, Josef
-
Boris Mulder -
Josef Söntgen