Hi Jukka,

>
> Hi Matti,
>
> On 13 October 2014 21:23, Matti Laakso <[email protected]> wrote:
>> Hi Jukka,
>>
>>>>
>>>> I'm running Yocto Linux 1.4 with connman 1.12 and wpa_supplicant 2.0. I
>
> Yep, Yocto 1.4 (dylan) has new dbus interface activated.
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/defconfig-gnutls?h=dylan
>
>>>>
>>>> # ./test-new-supplicant
>>>> ERROR:dbus.proxies:Introspect error on :1.2:/fi/w1/wpa_supplicant1:
>>>> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod:
>>>> wpa_supplicant was compiled without introspection support.
>
> This would really indicate an issue with new dbus interface but as you
> said it should be acticated in wpa_s.

This just indicated that CONFIG_CTRL_IFACE_DBUS_INTRO was not set. Adding it 
made
test-new-supplicant work, but didn't help with ConnMan.

>>>>
>>>> I'm able to connect wifi with wpa_supplicant alone.
>>>
>>> It looks like your wpa_supplicant is not compiled with new dbus API.
>>> So check from wpa_supplicant config file that you have
>>>
>>> # Add support for new DBus control interface
>>> # (fi.w1.hostap.wpa_supplicant1)
>>> CONFIG_CTRL_IFACE_DBUS_NEW=y
>>>
>>>
>>> Check also ConnMan README file, it contains information about the
>>> settings you need to activate in wpa_s.
>>>
>>
>> I do have CONFIG_CTRL_IFACE_DBUS_NEW enabled. I also tried
>> 'supplicant-test' (which seems to only use the new interface) with mixed 
>> results:
>>
>> # supplicant-test
>> supplicant: Startup
>> ^Csupplicant: Terminating
>> supplicant: Exit
>>
>> i.e., it fails to start wpa_supplicant with the new DBus interface. However, 
>> if I first
>> start wpa_supplicant by hand (wpa_supplicant -u -B), it works:
>>
>> # supplicant-test
>> supplicant: Startup
>> supplicant: service_property() Debug level 2
>> supplicant: service_property() Debug timestamp 0
>> supplicant: service_property() Debug show keys 0
>> supplicant: debug_strvalmap() EAP method: MD5
>> supplicant: debug_strvalmap() EAP method: TLS
>> supplicant: debug_strvalmap() EAP method: MSCHAPV2
>> supplicant: debug_strvalmap() EAP method: PEAP
>> supplicant: debug_strvalmap() EAP method: TTLS
>> supplicant: debug_strvalmap() EAP method: GTC
>> supplicant: debug_strvalmap() EAP method: OTP
>> supplicant: debug_strvalmap() EAP method: LEAP
>> supplicant: service_property() key Capabilities type a
>> supplicant: system_ready() *
>> ...
>>
>> and so on, detecting wlan0 and a bunch of networks. ConnMan still won't find 
>> wifi, however.
>> So it seems that the new interface is there, and works, but it can't be used 
>> to start
>> wpa_supplicant (even though the dbus service file is there and has correct 
>> content).
>> Could this be a permissions issue? I also think that out of the settings 
>> from ConnMan
>> README I'm missing CONFIG_WPS and CONFIG_AP, are they absolutely needed?
>> I'll try recompiling with them later.
>
> Yes, it could be a permission problem.
>

Turned out (see links to logs below) that supplicant-test doesn't even try to 
start
wpa_supplicant, so this is by design. It also turned out that ConnMan doesn't 
produce
any DBus traffic related to wpa_supplicant. Also, CONFIG_WPS and CONFIG_AP
didn't make a difference.

>
> Would you able to upgrade connman, with Yocto that is quite trivial.
>

I'll try that next.

> I have also used Yocto but newer version than what you are using and
> have had no issues with wifi. I had to specify some options for wpa_s
> that were not found in standard Yocto.
> See http://git.yoctoproject.org/cgit/cgit.cgi/meta-eca/ and
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-eca/tree/meta-eca/recipes-connectivity/wpa-supplicant
> for details.
>
>
> Cheers,
> Jukka

Here are two dbus-monitor logs with some explanations. First one from the 
various
test scripts, and the second one from starting connmand:
http://ltl.tkk.fi/~malaakso/misc/dbus.log
http://ltl.tkk.fi/~malaakso/misc/dbus2.log

Best regards,
Matti
                                          
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman

Reply via email to