Race condition on too fast stop&&start resulting in Error /net/connman/technology/wifi: Not supported that does not recovery without another restart
by KARBOWSKI Piotr
Hi,
I am facing issue with connman-1.37 regarding the wireless network
access. If I restart connman that was already running, I will get not
working wireless connection
# connmanctl scan wifi
Error /net/connman/technology/wifi: Not supported
I can reproduce it on two separated Gentoo ~amd64 systems. One has Intel
9462 and the other with Intel 8265. The wireless connection never
recovery unless I restart connman one more time.
If I not use restart, but stop && start with sleep 3 in between for
example, everything works.
It looks to me like a race condition with whatever connman does to
iwlwifi device upon stopping, that is still 'on going' after connmand
exited, and when new one starts, it lacks code to retry bringing device
up after a delay when it fails for the first time, unless it silently
fails inside, somewhere.
Steps to reproduce:
While connman is running, run /etc/init.d/connman stop &&
/etc/init.d/connman start
The `connmanctl scan wifi` will not work regardless of how long one will
wait. The init script is the most basic one, all it does is
starts/terminates /usr/sbin/connmand.
Steps to reproduce with a workaround:
While connman is running, run /etc/init.d/connman stop && sleep 3 &&
/etc/init.d/connman start
The `connmanctl scan wifi` will work after a few seconds.
-- Piotr.
2 months, 4 weeks
dnsproxy: invalid answer where there are no DNS servers available
by Nuno Gonçalves
Hi,
Typing "ping abcd", where abcd does not exist on /etc/hosts or in the
search domains, will usually hang for a while with Connman.
I've compared with other systems and my conclusion is that libnss_dns
is retrying the DNS request to connman, since connman answer does not
include the query field.
This behaviour comes from [1], where both a invalid Query and no
upstream servers are handled in the same way.
I believe the query field must be part of the answer when the Query
message was valid, but just happens to not be possible to resolve.
Thanks,
Nuno
[1] https://git.kernel.org/pub/scm/network/connman/connman.git/tree/src/dnspr...
4 months
Connman - handle multiple wifi interfaces
by Rahul Jain
Dear Connman,
I have a query.
Can Connman handle multiple wifi interfaces: like wlan0, wlan1 & wlan2 and
all are powered on?
If as per current architecture it is not possible, can you provide any
suggestions on how to handle it? Can we duplicate wifi plugin and
gsupplicant interface to handle both interface together.?
Please provide suggestions.
-Thank you
RJ
4 months, 2 weeks
[PATCH] gweb: fix segfault with musl v1.1.21
by Nicola Lunghi
In musl > 1.1.21 freeaddrinfo() implementation changed and
was causing a segmentation fault on recent Yocto using musl.
See this commit:
https://git.musl-libc.org/cgit/musl/commit/src/network/freeaddrinfo.c?id=...
---
gweb/gweb.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gweb/gweb.c b/gweb/gweb.c
index 393afe0a..12fcb1d8 100644
--- a/gweb/gweb.c
+++ b/gweb/gweb.c
@@ -1274,7 +1274,8 @@ static bool is_ip_address(const char *host)
addr = NULL;
result = getaddrinfo(host, NULL, &hints, &addr);
- freeaddrinfo(addr);
+ if(!result)
+ freeaddrinfo(addr);
return result == 0;
}
--
2.19.1
4 months, 2 weeks
[PATCH 00/10] Improve handling of VPN agent return types
by Jussi Laakkonen
The different returns from VPN agent should be handled accordingly in VPN
plugins as well as in connmand. Otherwise there will be a race between each
VPN agent supporting VPN type as canceling or timeouting the VPN agent dialog
would not unset the autoconnect value (to false) and change is not propagated to
service file written to disk. This will manifest itself after the next restart
of connmand as continuous connect-disconnect-connect loop between the VPNs that
were attempted to connect but their VPN agent dialog was canceled.
This set of patches enables processing of the different VPN agent return types
and ensures that autoconnect value changes are done internally and written to
disk. Improved processing of VPN agent return is used in the VPN plugins that
utilize it (L2TP, OpenConnect, PPTP and VPNC, OpenVPN is excluded) and a proper
reply is sent back to caller.
Each aforementioned plugin should not have own implementation of error checking
and thus, a generic one is implemented in vpn-agent.c. Processing of the error
is done using the callback of the VPN plugin, which eventually is
vpn-provider.c:connect_cb() that is also amended to support the different error
types. If there is no error returned from VPN agent normal operation is resumed.
The returned error is then passed to caller as appropriate D-Bus error message.
The caller (plugins/vpn.c) should be able to disable VPN autoconnect if the user
has cancelled the VPN agent dialog. For this the new error type
OperationCanceled (ECANCELED) is implemented and setters for autoconnect value
are created into provider.c and service.c.
Jussi Laakkonen (10):
vpn-agent: Implement generic D-Bus error checker for plugins.
vpn-provider: React to different error types in connect_cb()
l2tp: Use vpn-agent.c error processing for VPN agent errors.
openconnect: Use vpn-agent.c error processing for VPN agent errors.
pptp: Use vpn-agent.c error processing for VPN agent errors.
vpnc: Use vpn-agent.c error processing for VPN agent errors.
service: Implement function to set service autoconnect value
provider: Implement function to set VPN service autoconnect value
error: Implement OperationCanceled error type
vpn: Handle OperationCanceled D-Bus message reply
include/provider.h | 2 ++
include/service.h | 2 ++
plugins/vpn.c | 14 +++++++++++-
src/connman.h | 1 +
src/error.c | 8 +++++++
src/provider.c | 11 +++++++++
src/service.c | 12 ++++++++++
vpn/plugins/l2tp.c | 18 ++++++++++++---
vpn/plugins/openconnect.c | 11 +++++++--
vpn/plugins/pptp.c | 18 ++++++++++++---
vpn/plugins/vpnc.c | 40 +++++++-------------------------
vpn/vpn-agent.c | 48 +++++++++++++++++++++++++++++++++++++++
vpn/vpn-agent.h | 4 ++++
vpn/vpn-provider.c | 46 +++++++++++++++++++++++++++++++++++--
14 files changed, 192 insertions(+), 43 deletions(-)
--
2.20.1
4 months, 3 weeks
Failing to connect to service with manual provisioning
by Jason Tribe
Hi,
We are using the manual method of connecting to a service, where we write
the service config file to /var/lib/connman and then call the connect
function on that services interface without using the agent API.
The problem we are having is that this method results in a "Not registered"
error message in most cases. The only way we can get this to work correctly
is to disable and then enable the WiFi technology after writing the config
file and before calling the connect function on that service.
Has anyone had a similar issue or is there a better solution to connect to
a service without using the agent API.
Kind regards
Jason Tribe
4 months, 3 weeks
Failure state reset after wifi authentication denied
by Damien Miliche
Hi,
I've encountered a situation where an wifi Access Point denies the
authentication of my client ("denied authentication (status 17)").
Connman considers that as a failure, and the service I was trying to
connect enters the 'failure' state, with error 'connect-failed'.
From then, after only one attempt, despite the background scanning,
connman never tries to reconnect automatically, even if the service is
configured as 'AutoConnect' and the corresponding SSID appears in the
scan results: it looks like it is ignored.
Is that normal behaviour?
Is there a way for connman to consider the failed service in subsequent
automatic scan results (exponential bg scan) to retry connecting?
The only way I found so far is to manually trigger a connection, but
that is not acceptable for unattended device... :s
Thanks in advance for your help.
Kind regards,
--
Damien
4 months, 3 weeks
Changing vpn property through DBUS
by Salman Ahmed
Previous mail didn't appear as post.
Hello,
I am trying to change the properties of a vpn conection under connman
(through DBUS) but I am running into an error
e.g) This call succeeds and I am presented with the properties of the vpn
connection
dbus-send --system --dest=net.connman.vpn --type=method_call --print-reply
/net/connman/vpn/connection/uk_london_privateinternetaccess_com_privateinternetaccess_com
net.connman.vpn.Connection.GetProperties
Using d-feet I see that the SetProperty is defined as SetProperty (String
name, Variant value)->()
But if I do SetProperty like this
dbus-send --system --dest=net.connman.vpn --type=method_call --print-reply
/net/connman/vpn/connection/uk_london_privateinternetaccess_com_privateinternetaccess_com
net.connman.vpn.Connection.SetProperty string:Name variant:string:"NewName"
I get error > Error net.connman.Error.NotSupported: Not supported
I also tried it with the python test
./vpn-property
uk_london_privateinternetaccess_com_privateinternetaccess_com Name NewName
net.connman.Error.NotSupported: Not supported
5 months
In Progress Connman Error
by Bair, Richard
Here is some additional detail regarding in progress error when issuing a connect command via connmanctl.
*** Here I did a systemctl restart connman.service after changing the service file to include some debug per -d plugins/wifi.c ***
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1112]: Terminating
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1112]: Remove interface eth0 [ ethernet ]
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1112]: Remove interface wlan0 [ wifi ]
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1112]: eth0 {remove} index 2
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1112]: wlan0 {remove} index 4
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1112]: Exit
*** Above here looks like shutdown and restart happens here ***
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: Connection Manager version 1.35
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: Checking loopback interface settings
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: System hostname is var-som-mx6
Jun 11 12:55:36 var-som-mx6 daemon.err connmand[1132]: No IPv6 support
Jun 11 12:55:36 var-som-mx6 daemon.err connmand[1132]: No IPv6 support
Jun 11 12:55:36 var-som-mx6 daemon.err connmand[1132]: Failed to open RFKILL control device
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: lo {newlink} index 1 address 00:00:00:00:00:00 mtu 65536
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: lo {newlink} index 1 operstate 0 <UNKNOWN>
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: eth0 {create} index 2 type 1 <ETHER>
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: eth0 {update} flags 36866 <DOWN>
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: eth0 {newlink} index 2 address F8:DC:7A:13:B8:92 mtu 1500
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: eth0 {newlink} index 2 operstate 2 <DOWN>
Jun 11 12:55:36 var-som-mx6 daemon.info dbus-daemon[370]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.126' (uid=0 pid=1132 comm="/usr/sbin/connmand -n -d plugins/wifi.c ")
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: Adding interface eth0 [ ethernet ]
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: wlan0 {create} index 4 type 1 <ETHER>
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: wlan0 {RX} 51 packets 7988 bytes
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: wlan0 {TX} 65 packets 11313 bytes
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: wlan0 {update} flags 36867 <UP>
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: wlan0 {newlink} index 4 address 74:DA:38:EF:EC:93 mtu 1500
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: wlan0 {newlink} index 4 operstate 2 <DOWN>
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: Adding interface wlan0 [ wifi ]
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: wlan0 {RX} 51 packets 7988 bytes
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: wlan0 {TX} 65 packets 11313 bytes
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: wlan0 {newlink} index 4 address 74:DA:38:EF:EC:93 mtu 1500
Jun 11 12:55:36 var-som-mx6 daemon.info connmand[1132]: wlan0 {newlink} index 4 operstate 2 <DOWN>
Jun 11 12:55:37 var-som-mx6 daemon.warn connmand[1132]: Skipping disconnect of 52442d74657374696e67_managed_psk, network is connecting.
Jun 11 12:55:37 var-som-mx6 daemon.warn connmand[1132]: ipconfig state 2 ipconfig method 1
Jun 11 12:57:37 var-som-mx6 daemon.warn connmand[1132]: ipconfig state 7 ipconfig method 1
*** After reset I think this is where I'm in interactive mode and issue connect wifi_xxxx_xxxx and I receive an "In progress" error
Jun 11 12:58:12 var-som-mx6 daemon.warn connmand[1132]: Skipping disconnect of 52442d74657374696e67_managed_psk, network is connecting.
Jun 11 12:58:12 var-som-mx6 daemon.warn connmand[1132]: ipconfig state 2 ipconfig method 1
*** So, any idea why my connect is not occurring? ***
Thanks,
-Rich
5 months, 1 week
Baisc Connman Questions (sorry!)
by Bair, Richard
Ok, I'm prepared for the RTFM response but I could really use some fast-tracking!
1) I have an embedded Linux system based on a yocto image. So I have connman and wpa_supplicant.
2) From my reading to date I should use connman only and avoid the complexity of wpa_supplicant.
3) I plan to support WiFi interfaces only....Enterprise and WPA (no open networks)
Questions:
1) I noticed there is no /etc/connman/main.conf by default. I suppose if I create that file it will configure connman provided my syntax is correct?
2) I'm clear how to use connmanctl interactive mode to make a connection but I'm less clear on the process for my Qt application to perform this. I believe it would simply be a connmanctl connect call when a user configures a WiFi SSID. As connman persists over a reboot do I only issue the connect call when a user re-configures and on reboot provided connman and wpa_supplicant services are up the connection will attempt to re-establish?
3) I've noticed sometimes connman connections seem "In progress"...how can I force a connman abort and "reset" to get ready for a new command? Anyway to do this without restarting the connman service?
4) In my WPA, I'm a bit lost regarding how provisioning files work. When my user enters appropriate information is there a command I can call to build a provisioning file for the connection I've established? Does connman automatically update files like /etc/wpa_supplicant.conf?
Thanks,
-Rich
5 months, 1 week
