Send connman mailing list submissions to
        connman@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-requ...@lists.01.org

You can reach the person managing the list at
        connman-ow...@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 <w...@monom.org>
To: Christian Spielberger <christian.spielber...@gmail.com>,
        connman@lists.01.org
Subject: Re: Planning Address Conflict Detection RFC-5227
Message-ID: <dd2c1043-4bba-c1dc-faef-c480f3228...@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 <w...@monom.org>
To: ?? <1351706...@qq.com>, connman <connman@lists.01.org>
Subject: Re: connman gsupplicant EAP-TLS
Message-ID: <1fca81e0-c508-1323-1cae-fe4beab0d...@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 <w...@monom.org>
To: "1351706...@qq.com" <1351706...@qq.com>, connman
        <connman@lists.01.org>
Subject: Re: Does ConnMan support 802.1X authentication over wifi?
Message-ID: <2f1bd711-e1dc-0d00-82f2-7cb7a718d...@monom.org>
Content-Type: text/plain; charset=windows-1252

Hi,

On 07.02.2018 07:49, 1351706...@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 <w...@monom.org>
To: "1351706...@qq.com" <1351706...@qq.com>, connman
        <connman@lists.01.org>
Subject: Re: connman eap-tsl gsuuplicant connect error
Message-ID: <a1895356-feb7-ed34-60d8-80e37e3a1...@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@lists.01.org
https://lists.01.org/mailman/listinfo/connman


------------------------------

End of connman Digest, Vol 28, Issue 4
**************************************

Reply via email to