8:50 a.m.
Hi Jose,
On 08/10/2017 10:25 AM, Jose Blanquicet wrote:
On Tue, Aug 8, 2017 at 3:22 PM, Sam Nazarko
<email(a)samnazarko.co.uk> wrote:
> I can reproduce this issue. We wanted to disable BackgroundScanning as we support
> a few wireless drivers that experience disruption to the connection when scanning
> occurs. After disabling BackgroundScanning in ConnMan 1.34, we had numerous
> reports of users unable to find any WiFi networks.
What you need is to disable specifically what I explained as
Background-Scan for roaming proposes.
Here we could think to divide "BackgroundScanning" into two different
properties, one for Background-Scan another for Auto-Scan. What do
people think?
Not sure how to address this. I personally get confused by the terms background
scan and auto scan. The name 'auto' and 'background' are like synonyms in
my ears.
Furthermore, we should be careful to add main.conf config options which are
wpa_supplicant specific. We had this discussion already for other scenarios.
Adding low level config options it to main section of main.conf should be
avoided if you ask me. We have already a bunch of them.
The only idea I have so far to allow low-level plugin specific configuration
files. We would need to move of the connnman_config_*() bits around to the
public header files. Then plugins could use such function as:
char *__connman_config_get_string(GKeyFile *key_file,
const char *group_name, const char *key, GError **error);
char **__connman_config_get_string_list(GKeyFile *key_file,
const char *group_name, const char *key, gsize *length, GError **error);
bool __connman_config_get_bool(GKeyFile *key_file,
const char *group_name, const char *key, GError **error);
The reason why I suggest to allow plugins to open the keyfiles directly is that
I don't want to read all config data in the core and then pass it to
the plugin.
Sorry this is slightly detour but I think we could make use of these
changes to factor out the wpa_supplicant config hell from main.conf.
Thanks,
Daniel