Send connman mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: Unable to setup connman using systemd (Tomasz Bursztyka)
----------------------------------------------------------------------
Message: 1
Date: Thu, 13 Oct 2016 08:26:28 +0200
From: Tomasz Bursztyka <[email protected]>
To: [email protected]
Subject: Re: Unable to setup connman using systemd
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Hi Fabio,
Run "technologies" in connmanctl.
I bet wifi won't be part of the list.
Interfaces can be added, but if there is no technology to drive it, you
won't get control over these.
Is wpa_supplicant started to provide its dbus interface and not the unix
socket stuff? ( it should have -u option)
Tomasz
> Dear all,
>
> I'm trying to setup connman using systemd. When I try to execute the
> command:
>
>> connmanctl enable wifi
> I've got the following error:
>
>> Error wifi: Method "SetProperty" with signature "sv" on interface
>> "net.connman.Technology" doesn't exist
> I had the same error when I was using connman with the old SysVinit.
> After some tries I discovered that the cause of the error was the lack
> of the CONFIG_RFKILL=y in the kernel configuration options. After the
> enable of RFKILL everything had started to work.
>
> After the migration from SysVinit to systemd, connman doesn't want to
> see the wireless technology. The result is that connman can't control
> the wireless interface.
>
> Another bit of info:
>
> - I have RFKILL installed and correctly configured:
>
>> root@lam_icu:~# rfkill list 0
>> 0: phy0: Wireless LAN
>> Soft blocked: no
>> Hard blocked: no
> - wpa_supplicant is installed and configured to start before connman
>
> - the wireless interface is correctly configured, I can perform a
> scan, I can connect to a network using wpa_supplicant
>
> - if launching connmand manually I see the following log:
>
>> root@lam_icu:~# connmand -n
>> connmand[4026]: Connection Manager version 1.28
>> connmand[4026]: Checking loopback interface settings
>> connmand[4026]: System hostname is lam_icu
>> connmand[4026]: System domainname is artgroup
>> connmand[4026]: lo {newlink} index 1 address 00:00:00:00:00:00 mtu 65536
>> connmand[4026]: lo {newlink} index 1 operstate 0 <UNKNOWN>
>> connmand[4026]: sit0 {newlink} index 2 address 00:00:00:00:08:00 mtu 1480
>> connmand[4026]: sit0 {newlink} index 2 operstate 2 <DOWN>
>> connmand[4026]: usb0 {create} index 3 type 1 <ETHER>
>> connmand[4026]: usb0 {update} flags 36866 <DOWN>
>> connmand[4026]: usb0 {newlink} index 3 address 5E:88:F6:99:F3:4F mtu 1500
>> connmand[4026]: usb0 {newlink} index 3 operstate 2 <DOWN>
>> connmand[4026]: Adding interface usb0 [ gadget ]
>> connmand[4026]: eth0 {create} index 4 type 1 <ETHER>
>> connmand[4026]: eth0 {RX} 16657 packets 1338888 bytes
>> connmand[4026]: eth0 {TX} 0 packets 185445 bytes
>> connmand[4026]: eth0 {update} flags 36866 <DOWN>
>> connmand[4026]: eth0 {newlink} index 4 address 00:90:9A:9D:AC:B2 mtu 1500
>> connmand[4026]: eth0 {newlink} index 4 operstate 2 <DOWN>
>> connmand[4026]: Adding interface eth0 [ ethernet ]
>> *connmand[4026]: wlan0 {create} index 5 type 1 <ETHER>**
>> **connmand[4026]: wlan0 {update} flags 4098 <DOWN>**
>> **connmand[4026]: wlan0 {newlink} index 5 address DE:AD:BE:EF:00:00
>> mtu 1500**
>> **connmand[4026]: wlan0 {newlink} index 5 operstate 2 <DOWN>**
>> **connmand[4026]: Adding interface wlan0 [ wifi ]*
>> connmand[4026]: eth0 {RX} 16657 packets 1338888 bytes
>> connmand[4026]: eth0 {TX} 0 packets 185445 bytes
>> connmand[4026]: eth0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
>> connmand[4026]: eth0 {newlink} index 4 address 00:90:9A:9
> wlan0 is correctly added.
>
> What is in your opinion the cause of the problem? How can I debug the
> issue?
>
> Thanks in advance for your help
>
> Regards,
>
> Fabio Emiliani
>
> --
>
> *Fabio Emiliani*
>
> */Software Engineer/*
>
> /Ph. +39 075 8298 532/
>
> /[email protected]/ <mailto:[email protected]>
>
> DISCLAIMER
> This email and any attachment may contain confidential information. If
> you are not the intended recipient you are not authorised to copy or
> disclose all or any part of it without the prior written consent of
> ART SpA.
>
> /ART SpA ? Step Forward With US -
> //www.artgroup-spa.com/logo_ART_firma-1//
>
> /Ph. +39 075 8298 501 ? Fax +39 075 8298 525 /
>
> P*Please consider our environment before printing this e-mail***
>
>
>
> _______________________________________________
> connman mailing list
> [email protected]
> https://lists.01.org/mailman/listinfo/connman
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.01.org/pipermail/connman/attachments/20161013/1b81d7e3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 16420 bytes
Desc: not available
URL:
<http://lists.01.org/pipermail/connman/attachments/20161013/1b81d7e3/attachment.jpe>
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 12, Issue 8
**************************************
