The private data should be cleared on disconnect to avoid an invalid
access. For example the user could call disconnect twice which leads
to a crash.
vpn/plugins/wireguard.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/vpn/plugins/wireguard.c b/vpn/plugins/wireguard.c
index 061be789fa59..de2dbda3878e 100644
@@ -375,6 +375,10 @@ static void wg_disconnect(struct vpn_provider *provider)
struct wireguard_info *info;
info = vpn_provider_get_plugin_data(provider);
+ if (!info)
+ vpn_provider_set_plugin_data(provider, NULL);
Currently all connection attempts are reported as
CONNMAN_NETWORK_ERROR_CONNECT_FAIL. When the user enters an wrong
passphrase the upper layers wont reset the passphrase unless
CONNMAN_NETWORK_ERROR_INVALID_KEY is reported. This prevents the user
to enter a new passphrase.
Unfortunately, when the passphrase is correct but the connect attempt
fails with 'Failed', ConnMan will reset the passphrase. But this
behavoir is way better then not being able to provide the correct
Reported-by: Maxime Roussin-Bélanger <maxime.roussinbelanger(a)gmail.com>
plugins/iwd.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/plugins/iwd.c b/plugins/iwd.c
index 7b5d9b92d658..39879f6f8c87 100644
@@ -241,7 +241,11 @@ static void cm_network_connect_cb(DBusMessage *message, void *user_data)
DBG("%s connect failed: %s", path, dbus_error);
+ if (!strcmp(dbus_error, "net.connman.iwd.Failed"))
I started to use connman 1.37 with YOCTO (pyro)
I observed the connman 1.37 source code that YOCTO uses is different
from the source code in
To be more precise, I cannot find ipv4ll.c file in YOCTO source code.
I enabled the wlan0 interface but did not connect to any network. I
see my log if filled with these messages:
wlcore: firmware booted (Rev 220.127.116.11.142)
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
I didn't see this behavior on connman 1.35 version,
We are on version 1.37, we are using wpa_supplicant 2.9 with a kernel 4.19. When we are trying to use the connmanctl to connect to a protected wifi network it works well without a problem. However, if we make a mistake when we type the passphrase, it's impossible to retry. It does that to any network that we have tried.
It is impossible to retry because for some reason when we are asked to retry (https://git.kernel.org/pub/scm/network/connman/connman.git/tree/client/ag...), this gets "cancel" by the agent
(https://git.kernel.org/pub/scm/network/connman/connman.git/tree/client/ag...) and we lose the ability to retry forever for this network unless we delete the settings for this particular network. I never get a chance to enter yes or no. It never enters the callback (https://git.kernel.org/pub/scm/network/connman/connman.git/tree/client/ag...), that was set at line 365 in client/agent.c
We looked at the d-bus-monitor and we get two types of error: `-3` and we do get a `16`, from 80211 AssocCode status code. -3 from what I can understand is internal.
Now, since I have not seen this issue from others, I'm wondering if it's related to our wifi chip misbehaving? I heard about a new thing called `iwd`, but I haven't tested it, maybe I could give this a shot.
I'm using connman version 1.36 and wpa_supplicant 2.36.
I have a couple of issues with wifi scan and setting static IP address for
wlan0 interface, could you please help me resolve this?
1. When I scan periodically ( every 10seconds), connman hangs up. Is there any
configuration in connman or wpa_supplicant that can resolve this?
2. When the connected wireless network goes out of range or when i power
off the wireless router to which I'm connected, wifi scan hangs up. this is
the error message that I receive
*"Error /net/connman/technology/wifi: Did not receive a reply. Possible
causes include: the remote application did not send a reply, the message
bus security policy blocked the re."*
3. How do I set up a static IP for wlan0 interface?