connman built with `--disable-ethernet` wipe ethernet interface configuration on start anyway
by KARBOWSKI Piotr
Hi,
I have connman built with `--disable-ethernet`. However, every time I
start connmand, the configuration of eth0 interface is wiped.
Is there a way to make connman not touch my wired interfaces? I tried to
set 'Enabled' option in /var/lib/connman/settings to both true and false
in the '[Wired]' part, but nothing changed, connman keeps wiping my
runtime configuration.
-- Piotr.
2 years, 11 months
[RFC 0/3] Only cleanup devices which are supported
by Daniel Wagner
Hi,
When ConnMan starts up, it wipes all configuration on all
interfaces instead only those interfaces it will control.
This series fixes this by spliting the plugin init step into two
steps. The first is to register the technology driver and the second
does the rest. This split is needed because the plugin initilization
happens after the cleanup step. The plugin technology registration
happens before the cleanup so we can now filter which interface we
will cleanup or not. So far the theory.
I don't really like the first patch. It touches all plugins and adds
some noise to those plugins which do not need to set the
technology. Maybe with some precompiler black magic things could help,
but that sounds even worse. Another idea is to introduce an another
indiration for the initilization steps. Every plugin registers an
init/cleanup function pointer table. So we would have an explicit
registration step for the different drivers and one for the final init
step. Currently every plugin does it's own thing with different kind
of error handling. Well, error handling seems anyway a bit
missing. The plugins return error code and the core just jumps over
it.
Any thoughs?
Reported-by: KARBOWSKI Piotr <piotr.karbowski(a)gmail.com>
Daniel Wagner (3):
plugins: Introduce explicit technology un/register
technology: Add __connman_technology_is_supported()
device: Only cleanup devices which are supported
include/plugin.h | 32 ++++++++++++++++++++++-----
plugins/bluetooth.c | 21 ++++++++++--------
plugins/dundee.c | 3 ++-
plugins/ethernet.c | 19 ++++++++++------
plugins/gadget.c | 21 +++++++++++-------
plugins/loopback.c | 3 ++-
plugins/neard.c | 3 ++-
plugins/nmcompat.c | 2 +-
plugins/ofono.c | 21 ++++++++++--------
plugins/pacrunner.c | 3 ++-
plugins/polkit.c | 3 ++-
plugins/session_policy_local.c | 3 ++-
plugins/vpn.c | 3 ++-
plugins/wifi.c | 22 ++++++++++---------
src/connman.h | 6 ++++-
src/device.c | 5 +++++
src/main.c | 6 ++++-
src/plugin.c | 50 ++++++++++++++++++++++++++++++++++++------
src/technology.c | 5 +++++
vpn/main.c | 2 +-
vpn/plugins/openconnect.c | 3 ++-
vpn/plugins/openvpn.c | 3 ++-
vpn/plugins/vpnc.c | 3 ++-
23 files changed, 173 insertions(+), 69 deletions(-)
--
2.14.3
2 years, 11 months
Re: connman Digest, Vol 28, Issue 4
by Daniel Wagner
Hi,
On 02/10/2018 03:54 AM, 1351706412(a)qq.com wrote:
>
> hi Daniel,
> i see "man connman-service.config", and connect ieee802.1x tls
> method type Wifi.
> i really really try many many times to config the parser, but connmanctl
> report
> "Error /net/connman/service/wifi_7cdd90caf78b_526f79_managed_ieee8021x:
> Input error"
> my "/usr/local/var/lib/connman/tls.config" as follows
>
> [service_tls]
> Type = wifi
> SSID = Roy
> EAP = tls
> CACertFile = /home/echo/work/user/tls/ca.pem
> ClientCertFile = /home/echo/work/user/tls/client.p12
> PrivateKeyFile = /home/echo/work/user/tls/client.key
> Identity = user
> PrivateKeyPassphraseType = fsid
So first thing to look out if you see something like this here:
connmand[1672]: Config file /var/lib/connman/wpa-eap-testing.config
does not contain any configuration that can be provisioned!
In this case the config file somehow invalid. I checked your
configuration by hand and it looks syntactical correct.
One thing which is not correct is 'SSID = Roy'. The SSID field
is expected to be the hex representation of the name. Try instead
'Name = Roy'. It took me a while to spot it :)
> and now i have files named "ca.pem, client.pem, client.p12" on my
> freeradius centos server,
> i am not sure that the
> "PrivateKeyFile = /home/user/.certs/client.fsid.pem,
> PrivateKeyPassphraseType = fsid,
> Identity = user" is right or not?
This depends on your certificates if I am not completely wrong
here. If the key needs to unlocked by a passphrase.
So in case you still have problems, we need to look at the
wpa_supplicant/ConnMan interaction.
For example during my testing I got:
connmand[5161]: src/service.c:connect_service() service 0x205f6b0
connmand[5161]: src/service.c:__connman_service_connect() service 0x205f6b0 state idle connect reason none -> user
connmand[5161]: src/service.c:__connman_service_clear_error() service 0x205f6b0
connmand[5161]: src/service.c:__connman_service_connect() service 0x205f6b0 err -22
connmand[5161]: src/network.c:__connman_network_disconnect() network 0x2058560
So the -22 maps to EINVAL. Looking a bit at the code it is clear what is
happening.
static int service_connect(struct connman_service *service)
{
[...]
case CONNMAN_SERVICE_SECURITY_8021X:
if (!service->eap)
return -EINVAL;
[...]
}
ConnMan is not able to match the provisioning to the services.
So if you change your configuration file as described above
it should work (famous last words).
I just sent out a patch which adds a warning to log if we hit this
problem.
HTH,
Daniel
2 years, 11 months
Re: Re: Does ConnMan support 802.1X authentication over wifi?
by 1351706412＠qq.com
hi Vasyl,
i see "man connman-service.config", and connect ieee802.1x tls method type Wifi.
i really really try many many times to config the parser, but connmanctl report
"Error /net/connman/service/wifi_7cdd90caf78b_526f79_managed_ieee8021x: Input error"
my "/usr/local/var/lib/connman/tls.config" as follows
[service_tls]
Type = wifi
SSID = Roy
EAP = tls
CACertFile = /home/echo/work/user/tls/ca.pem
ClientCertFile = /home/echo/work/user/tls/client.p12
PrivateKeyFile = /home/echo/work/user/tls/client.key
Identity = user
PrivateKeyPassphraseType = fsid
and now i have files named "ca.pem, client.pem, client.p12" on my freeradius centos server,
i am not sure that the "PrivateKeyFile = /home/user/.certs/client.fsid.pem, PrivateKeyPassphraseType = fsid,
Identity = user" is right or not?
Thanks,
Vasyl
1351706412(a)qq.com
From: Vasyl Vavrychuk
Date: 2018-02-07 23:27
To: 1351706412(a)qq.com
Subject: Re: Does ConnMan support 802.1X authentication over wifi?
You have to write provision file with connection parameters in the
case of 802.1X, see 'man connman-service.config'
On Wed, Feb 7, 2018 at 8:49 AM, 1351706412(a)qq.com <1351706412(a)qq.com> wrote:
> Hi all,
>
> My team 's network requires 802.1X authentication for wifi. I can connect to
> it with my Arch Linux machine using dhcpcd and wpa-supplicant, but despite
> various efforts I haven't been able to write a working ConnMan profile. On
> the other hand, connecting to our Eduroam network via wifi works as
> expected.
>
> Am I missing something or doesn't ConnMan support 802.1X authentication over
> wifi at all?
>
> Best wishes
>
> ________________________________
>
>
> _______________________________________________
> connman mailing list
> connman(a)lists.01.org
> https://lists.01.org/mailman/listinfo/connman
>
2 years, 11 months
Re: connman Digest, Vol 28, Issue 4
by 1351706412＠qq.com
hi Daniel,
i see "man connman-service.config", and connect ieee802.1x tls method type Wifi.
i really really try many many times to config the parser, but connmanctl report
"Error /net/connman/service/wifi_7cdd90caf78b_526f79_managed_ieee8021x: Input error"
my "/usr/local/var/lib/connman/tls.config" as follows
[service_tls]
Type = wifi
SSID = Roy
EAP = tls
CACertFile = /home/echo/work/user/tls/ca.pem
ClientCertFile = /home/echo/work/user/tls/client.p12
PrivateKeyFile = /home/echo/work/user/tls/client.key
Identity = user
PrivateKeyPassphraseType = fsid
and now i have files named "ca.pem, client.pem, client.p12" on my freeradius centos server,
i am not sure that the "PrivateKeyFile = /home/user/.certs/client.fsid.pem, PrivateKeyPassphraseType = fsid,
Identity = user" is right or not?
Thanks,
Daniel
1351706412(a)qq.com
From: connman-request
Date: 2018-02-10 04:00
To: connman
Subject: connman Digest, Vol 28, Issue 4
Send connman mailing list submissions to
connman(a)lists.01.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
connman-request(a)lists.01.org
You can reach the person managing the list at
connman-owner(a)lists.01.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: Planning Address Conflict Detection RFC-5227 (Daniel Wagner)
2. Re: connman gsupplicant EAP-TLS (Daniel Wagner)
3. Re: Does ConnMan support 802.1X authentication over wifi?
(Daniel Wagner)
4. Re: connman eap-tsl gsuuplicant connect error (Daniel Wagner)
----------------------------------------------------------------------
Message: 1
Date: Fri, 9 Feb 2018 16:24:19 +0100
From: Daniel Wagner <wagi(a)monom.org>
To: Christian Spielberger <christian.spielberger(a)gmail.com>,
connman(a)lists.01.org
Subject: Re: Planning Address Conflict Detection RFC-5227
Message-ID: <dd2c1043-4bba-c1dc-faef-c480f322853a(a)monom.org>
Content-Type: text/plain; charset=utf-8
Hi Christian,
sorry for the late response due $reason...
On 07.02.2018 11:03, Christian Spielberger wrote:
> Hello,
>
> We are planning to add Address Conflict Detection RFC-5227 into connman.
Nice :)
> It will
> be my task to implement the main aspects of this RFC in the next 2-3 weeks.
> Now I will start by cloning the project to github. Then looking where and how
> to place the ACD code. If you have any hints, please let me know!
I would start by looking what we have in gdhcp/client.c. There is some
code in there for L2/L3 handling. From a quick glance in the RFC it
looks like the right place to start.
> The goal would be definitely to bring it upstream.
That is highly appreciated!
Thanks,
Daniel
------------------------------
Message: 2
Date: Fri, 9 Feb 2018 16:32:48 +0100
From: Daniel Wagner <wagi(a)monom.org>
To: ?? <1351706412(a)qq.com>, connman <connman(a)lists.01.org>
Subject: Re: connman gsupplicant EAP-TLS
Message-ID: <1fca81e0-c508-1323-1cae-fe4beab0d208(a)monom.org>
Content-Type: text/plain; charset=gb18030
Hi,
On 06.02.2018 13:29, ?? wrote:
> Hi Daniel,
>
> ? ? ? ? ? ? now I am major in the EAP-TLS method in 802.1x wifi
> Enterprise and want to use the gsupplicant to archieve it by dbus
> interface.?
> ? ? ? ? ? ? and I do try the related "supplicant-test" under the file of
> tools, i think some of gsupplicant functions of that can be borrowed,
> but i am not sure if gsupplicant related functions can be used for
> EAP-TLS method of 802.1x wifi Enterprise ca. have any suggestions?
The enterprise configuration is not possible through D-Bus. You need to
provide the configuration via the config file interface. See
connman/docs/config-format.txt
> ? ? ? ? ? ? and another i run the toos/supplicant-test and use
> dbus-monitor --system to catch
> dbus data, but get some errors like as follows:
>
> ? ? ? ? ? ? {
> ? ? ? ? ? ? ? ?...
> method call time=1517919527.400354 sender=:1.203 ->
> destination=fi.w1.wpa_supplicant1 serial=14
> path=/fi/w1/wpa_supplicant1/Interfaces/3;
> interface=fi.w1.wpa_supplicant1.Interface; member=Scan
> ? ?array [
> ? ? ? dict entry(
> ? ? ? ? ?string "Type"
> ? ? ? ? ?variant ? ? ? ? ? ? string "passive"
> ? ? ? )
> ? ?]
> method return time=1517919527.400374 sender=:1.102 -> destination=:1.203
> serial=10859 reply_serial=14
> signal time=1517919527.400377 sender=:1.102 -> destination=(null
> destination) serial=10860
> path=/fi/epitest/hostap/WPASupplicant/Interfaces/2;
> interface=fi.epitest.hostap.WPASupplicant.Interface; member=StateChange
> ? ?string "SCANNING"
> ? ?string "INACTIVE"
> error time=1517919527.400385 sender=org.freedesktop.DBus ->
> destination=:1.102error_name=org.freedesktop.DBus.Error.AccessDenied
> reply_serial=10860
> ? ?string "Rejected receive message, 2 matched rules; type="signal",
> sender=":1.102" (uid=0 pid=5690 comm="wpa_supplicant -Dnl80211,wext
> -iwlan0 -c/etc/wpa_s")
> interface="fi.epitest.hostap.WPASupplicant.Interface"
> member="StateChange" error name="(unset)" requested_reply="0"
> destination="org.freedesktop.DBus" (uid=1000 pid=1319
> comm="upstart-dbus-bridge --daemon --system --user --bus")"
> signal time=1517919527.400391 sender=:1.102 -> destination=(null
> destination) serial=10861
> path=/fi/epitest/hostap/WPASupplicant/Interfaces/2;
> interface=fi.epitest.hostap.WPASupplicant.Interface; member=Scanning
> ? ?boolean true
> error time=1517919527.400396 sender=org.freedesktop.DBus ->
> destination=:1.102 error_name=org.freedesktop.DBus.Error.AccessDenied
> reply_serial=10861
> ? ?string "Rejected receive message, 2 matched rules; type="signal",
> sender=":1.102" (uid=0 pid=5690 comm="wpa_supplicant -Dnl80211,wext
> -iwlan0 -c/etc/wpa_s")
> interface="fi.epitest.hostap.WPASupplicant.Interface" member="Scanning"
> error name="(unset)" requested_reply="0"
> destination="org.freedesktop.DBus" (uid=1000 pid=1319
> comm="upstart-dbus-bridge --daemon --system --user --bus")"
> signal time=1517919527.404433 sender=:1.102 -> destination=(null
> destination) serial=10862 path=/fi/w1/wpa_supplicant1/Interfaces/3;
> interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
>
> ? ? ? ? ? ? ? ?...
> ? ? ? ? ? ? ?}
>
> ? ? ? ? ? ? so in my ubuntu 16.04 physical pc, have any advices for
> solving it?
org.freedesktop.DBus.Error.AccessDenied sounds like the D-Bus
configuration is not correct for either ConnMan or wpa_supplicant. Check
if in /etc/d-bus/ is set everything correctly. For ConnMan we have a
template in the source tree for the D-Bus configuration. If you use the
wpa_supplicant from the distro it should usually work.
> and i do not connect wifi_* when under the connmanctl,
> actually i have the configuration file of eduroam.config
> thanks all.
If ConnMan has problems to communicate with wpa_supplicant it is no
supprise you don't see the wifi technology.
And if everything looks alright, you should try a different version of
wpa_supplicant. It is a constant source of problems. The D-Bus interface
changes subtle over time and ConnMan get's confused.
HTH,
Daniel
------------------------------
Message: 3
Date: Fri, 9 Feb 2018 16:36:31 +0100
From: Daniel Wagner <wagi(a)monom.org>
To: "1351706412(a)qq.com" <1351706412(a)qq.com>, connman
<connman(a)lists.01.org>
Subject: Re: Does ConnMan support 802.1X authentication over wifi?
Message-ID: <2f1bd711-e1dc-0d00-82f2-7cb7a718d1d9(a)monom.org>
Content-Type: text/plain; charset=windows-1252
Hi,
On 07.02.2018 07:49, 1351706412(a)qq.com wrote:
> Hi all,
>
> My team 's network requires 802.1X authentication for wifi. I can
> connect to it with my Arch Linux machine using dhcpcd and
> wpa-supplicant, but despite various efforts I haven't been able to write
> a working ConnMan profile. On the other hand, connecting to our Eduroam
> network via wifi works as expected.
>
> Am I missing something or doesn't ConnMan support 802.1X authentication
> over wifi at all?
ConnMan supports 802.1X via Wifi. Basically all the 802.1X
authentication steps are done by wpa_supplicant. ConnMan only passes the
necessary information from the configuration file to wpa_supplicant. So
if you are able to get a connection via wpa_supplicant using dhcpcd you
should also be able get it working with ConnMan.
Note the config file parser is extremely picky and not very verbose.
That means if you have a key string not as ConnMan expects it just
doesn't work. The parser really really needs some love and let the user
know if something is not as it should be.
HTH,
Daniel
------------------------------
Message: 4
Date: Fri, 9 Feb 2018 16:39:08 +0100
From: Daniel Wagner <wagi(a)monom.org>
To: "1351706412(a)qq.com" <1351706412(a)qq.com>, connman
<connman(a)lists.01.org>
Subject: Re: connman eap-tsl gsuuplicant connect error
Message-ID: <a1895356-feb7-ed34-60d8-80e37e3a1807(a)monom.org>
Content-Type: text/plain; charset=windows-1252
Hi,
> yes, i debug the connmand source code and config the eduroam
> configuration file and it works.
Sorry to hear this. The error reporting of the config code is not good
to say mildly. :(
> but i now want to connect the ieee8021x wifi network via connmanctl,
> ?any advice to me?
So from the error messsage I would say some of the arguments/parameters
are not passed to wpa_supplicant to work correctly. For example the keys
are case sensitive.
Thanks,
Daniel
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
connman(a)lists.01.org
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 28, Issue 4
**************************************
2 years, 11 months
Re: connman eap-tsl gsuuplicant connect error
by Daniel Wagner
Hi,
> yes, i debug the connmand source code and config the eduroam
> configuration file and it works.
Sorry to hear this. The error reporting of the config code is not good
to say mildly. :(
> but i now want to connect the ieee8021x wifi network via connmanctl,
> any advice to me?
So from the error messsage I would say some of the arguments/parameters
are not passed to wpa_supplicant to work correctly. For example the keys
are case sensitive.
Thanks,
Daniel
2 years, 11 months
Re: Does ConnMan support 802.1X authentication over wifi?
by Daniel Wagner
Hi,
On 07.02.2018 07:49, 1351706412(a)qq.com wrote:
> Hi all,
>
> My team 's network requires 802.1X authentication for wifi. I can
> connect to it with my Arch Linux machine using dhcpcd and
> wpa-supplicant, but despite various efforts I haven't been able to write
> a working ConnMan profile. On the other hand, connecting to our Eduroam
> network via wifi works as expected.
>
> Am I missing something or doesn't ConnMan support 802.1X authentication
> over wifi at all?
ConnMan supports 802.1X via Wifi. Basically all the 802.1X
authentication steps are done by wpa_supplicant. ConnMan only passes the
necessary information from the configuration file to wpa_supplicant. So
if you are able to get a connection via wpa_supplicant using dhcpcd you
should also be able get it working with ConnMan.
Note the config file parser is extremely picky and not very verbose.
That means if you have a key string not as ConnMan expects it just
doesn't work. The parser really really needs some love and let the user
know if something is not as it should be.
HTH,
Daniel
2 years, 11 months
connman gsupplicant EAP-TLS
by 师源
Hi Daniel,
now I am major in the EAP-TLS method in 802.1x wifi Enterprise and want to use the gsupplicant to archieve it by dbus interface.
and I do try the related "supplicant-test" under the file of tools, i think some of gsupplicant functions of that can be borrowed, but i am not sure if gsupplicant related functions can be used for EAP-TLS method of 802.1x wifi Enterprise ca. have any suggestions?
and another i run the toos/supplicant-test and use dbus-monitor --system to catch
dbus data, but get some errors like as follows:
{
...
method call time=1517919527.400354 sender=:1.203 -> destination=fi.w1.wpa_supplicant1 serial=14 path=/fi/w1/wpa_supplicant1/Interfaces/3; interface=fi.w1.wpa_supplicant1.Interface; member=Scan
array [
dict entry(
string "Type"
variant string "passive"
)
]
method return time=1517919527.400374 sender=:1.102 -> destination=:1.203 serial=10859 reply_serial=14
signal time=1517919527.400377 sender=:1.102 -> destination=(null destination) serial=10860 path=/fi/epitest/hostap/WPASupplicant/Interfaces/2; interface=fi.epitest.hostap.WPASupplicant.Interface; member=StateChange
string "SCANNING"
string "INACTIVE"
error time=1517919527.400385 sender=org.freedesktop.DBus -> destination=:1.102 error_name=org.freedesktop.DBus.Error.AccessDenied reply_serial=10860
string "Rejected receive message, 2 matched rules; type="signal", sender=":1.102" (uid=0 pid=5690 comm="wpa_supplicant -Dnl80211,wext -iwlan0 -c/etc/wpa_s") interface="fi.epitest.hostap.WPASupplicant.Interface" member="StateChange" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (uid=1000 pid=1319 comm="upstart-dbus-bridge --daemon --system --user --bus")"
signal time=1517919527.400391 sender=:1.102 -> destination=(null destination) serial=10861 path=/fi/epitest/hostap/WPASupplicant/Interfaces/2; interface=fi.epitest.hostap.WPASupplicant.Interface; member=Scanning
boolean true
error time=1517919527.400396 sender=org.freedesktop.DBus -> destination=:1.102 error_name=org.freedesktop.DBus.Error.AccessDenied reply_serial=10861
string "Rejected receive message, 2 matched rules; type="signal", sender=":1.102" (uid=0 pid=5690 comm="wpa_supplicant -Dnl80211,wext -iwlan0 -c/etc/wpa_s") interface="fi.epitest.hostap.WPASupplicant.Interface" member="Scanning" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (uid=1000 pid=1319 comm="upstart-dbus-bridge --daemon --system --user --bus")"
signal time=1517919527.404433 sender=:1.102 -> destination=(null destination) serial=10862 path=/fi/w1/wpa_supplicant1/Interfaces/3; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
...
}
so in my ubuntu 16.04 physical pc, have any advices for solving it? and i do not connect wifi_* when under the connmanctl, actually i have the configuration file of eduroam.config
thanks all.
2 years, 11 months
Does ConnMan support 802.1X authentication over wifi?
by 1351706412＠qq.com
Hi all,
My team 's network requires 802.1X authentication for wifi. I can connect to it with my Arch Linux machine using dhcpcd and wpa-supplicant, but despite various efforts I haven't been able to write a working ConnMan profile. On the other hand, connecting to our Eduroam network via wifi works as expected.
Am I missing something or doesn't ConnMan support 802.1X authentication over wifi at all?
Best wishes
2 years, 11 months
connman eap-tsl gsuuplicant connect error
by 1351706412＠qq.com
hi all,
I'm playing with connman on my Ubuntu 16.04 pc and get "Error /net/connman/service/wifi_7cdd90caf78b_526f79_managed_ieee8021x: Invalid arguments" error
when trying to do a wifi connect eap 802.1x . Could someone please point me towards the right direction or give some hints on how to solve this question.
Here's some details from my commanctl line:
(1)
connmanctl> services
*AO Wired ethernet_10c37ba06361_cable
* TP-LINK_1F81 wifi_7cdd90caf78b_54502d4c494e4b5f31463831_managed_psk
Roy wifi_7cdd90caf78b_526f79_managed_ieee8021x
ChinaNet-pVXz wifi_7cdd90caf78b_4368696e614e65742d7056587a_managed_psk
ChinaNet-WVDn wifi_7cdd90caf78b_4368696e614e65742d5756446e_managed_psk
STWW wifi_7cdd90caf78b_53545757_managed_psk
68 wifi_7cdd90caf78b_3638_managed_psk
localhost.localdomain wifi_7cdd90caf78b_6c6f63616c686f73742e6c6f63616c646f6d61696e_managed_psk
LeRen_2.4 wifi_7cdd90caf78b_4c6552656e5f322e34_managed_psk
QianXun_Main wifi_7cdd90caf78b_5169616e58756e5f4d61696e_managed_psk
wifi wifi_7cdd90caf78b_77696669_managed_psk
ChinaNet-JeZ5 wifi_7cdd90caf78b_4368696e614e65742d4a655a35_managed_psk
ChinaNet-zwns wifi_7cdd90caf78b_4368696e614e65742d7a776e73_managed_psk
QTQ2.4 wifi_7cdd90caf78b_515451322e34_managed_psk
VATICS_SZ_2.4G wifi_7cdd90caf78b_5641544943535f535a5f322e3447_managed_psk
ChinaNet-rPhW wifi_7cdd90caf78b_4368696e614e65742d72506857_managed_psk
(2)
connmanctl> connect wifi_7cdd90caf78b_526f79_managed_ieee8021x
Error /net/connman/service/wifi_7cdd90caf78b_526f79_managed_ieee8021x: Invalid arguments
yes, i debug the connmand source code and config the eduroam configuration file and it works.
but i now want to connect the ieee8021x wifi network via connmanctl, any advice to me?
thanks all.
2 years, 11 months
