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. Specify rules and routing tables for individual service
      (Liang, Jian [TYCO GBS - Cork])
   2. Re: Unable to setup connman using systemd (Fabio Emiliani)


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

Message: 1
Date: Thu, 13 Oct 2016 15:32:29 +0000
From: "Liang, Jian [TYCO GBS - Cork]" <jianli...@tycoint.com>
To: "connman@lists.01.org" <connman@lists.01.org>
Subject: Specify rules and routing tables for individual service
Message-ID:
        
<3b409afa23191042a221fe4d8b5c636031b...@003fch1mpn2-041.003f.mgd2.msft.net>
        
Content-Type: text/plain; charset="us-ascii"

Hi,

I have some questions here about connman regards to dealing with multiple 
services (network interfaces). My requirement is about source routing different 
type of packets from applications over different network interfaces through 
different routes. I understand that connman, by default, is maintaining one 
service in online state and using its gateway as the default gateway in the 
default routing table. The questions are

a.       Can I use connman APIs generate multiple routing tables and rules for 
source routing purpose?

b.      If not, can I obtain gateway addresses of services in ready state 
through connman APIs?

c.       If not, what would be the suggestion to achieve sourcing routing by 
using connman?

Kind regards,
Jian



________________________________

This e-mail contains privileged and confidential information intended for the 
use of the addressees named above. If you are not the intended recipient of 
this e-mail, you are hereby notified that you must not disseminate, copy or 
take any action in respect of any information contained in it. If you have 
received this e-mail in error, please notify the sender immediately by e-mail 
and immediately destroy this e-mail and its attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.01.org/pipermail/connman/attachments/20161013/24edae78/attachment-0001.html>

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

Message: 2
Date: Thu, 13 Oct 2016 18:31:51 +0200
From: Fabio Emiliani <fabio.emili...@artgroup-spa.com>
To: connman@lists.01.org
Subject: Re: Unable to setup connman using systemd
Message-ID: <899a3c38-c9bc-a5bd-a770-cda6d7503...@artgroup-spa.com>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"

Dear all,

I solved! The problem was the enable of the wifi plugin at connman 
compilation time. I don't know why but for some reasons my Yocto build 
lacks of the option:

> DISTRO_FEATURES_append += "wifi"
After the add of this option in local.conf, connman was succesfully 
build with the "--enable-wifi" option.

Many thanks for your support

Regards,

Fabio Emiliani

Il 13/10/2016 15:41, Tomasz Bursztyka ha scritto:
> What about Patrik's proposal?
>
> To me it sounds like a bus access authorization issue.
>
> Tomasz
>
>> Hi Tomasz,
>>
>> I've checked the build config of wpa_supplicant. The old 
>> "fi.epitest.hostap.WPASupplicant" interfaces is enabled for backward 
>> compatibility (CONFIG_CTRL_IFACE_DBUS=y). At the same time there is 
>> also the new "fi.w1.hostap.wpa_supplicant1" interface 
>> (CONFIG_CTRL_IFACE_DBUS_NEW=y).
>>
>> The service is correctly exposed. I tried to execute the following 
>> command:
>>
>>> dbus-send --system --dest=fi.w1.wpa_supplicant1 --type=method_call 
>>> --print-reply /fi/w1/wpa_supplicant1 
>>> fi.w1.wpa_supplicant1.*GetInterface* string:*wlan0*
>> GetInterface = Returns a D-Bus path to an object related to an 
>> interface which wpa_supplicant already controls
>>
>> And I've got the expected answer:
>>
>>> <nt1 fi.w1.wpa_supplicant1.GetInterface string:wlan0
>>> method return sender=:1.0 -> dest=:1.16 reply_serial=2
>>> *object path "/fi/w1/wpa_supplicant1/Interfaces/1"*
>> so the wlan0 interfaced is correctly controlled by the supplicant and 
>> the supplicant can be correctly controlled via the 
>> fi.w1.wpa_supplicant1 service.
>>
>> Supposing that wpa_supplicant is correctly configured, what other 
>> actors can cause the "No matching drivers found for wifi."?
>>
>> Regards,
>>
>> Fabio
>>
>> Il 13/10/2016 13:03, Tomasz Bursztyka ha scritto:
>>> Hi Fabio,
>>>
>>> It seems right. So then the issue is somewhere else, but still 
>>> related to DBus.
>>>
>>> Either connman has not the authorization to access wpa_s dbus 
>>> service, or
>>> wpa_s service is badly exposed (systemd config?) etc...
>>>
>>> Hard to tell, it's been a while since I have had such issue
>>>
>>> Tomasz
>>>
>>>> Tomasz,
>>>>
>>>> you are right. I launched wpa_supplicant and then connmand. Nothing 
>>>> has appeared on wpa_supplicant stdout.
>>>>
>>>> This is my wpa_supplicant dbus configuration file:
>>>>
>>>>> < cat /etc/dbus-1/system.d/dbus-wpa_supplicant.conf
>>>>> <!DOCTYPE busconfig PUBLIC
>>>>>  "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
>>>>> "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";>
>>>>> <busconfig>
>>>>>         <policy user="root">
>>>>>                 <allow own="fi.epitest.hostap.WPASupplicant"/>
>>>>>
>>>>>                 <allow 
>>>>> send_destination="fi.epitest.hostap.WPASupplicant"/>
>>>>>                 <allow 
>>>>> send_interface="fi.epitest.hostap.WPASupplicant"/>
>>>>>
>>>>>                 <allow own="fi.w1.wpa_supplicant1"/>
>>>>>
>>>>>                 <allow send_destination="fi.w1.wpa_supplicant1"/>
>>>>>                 <allow send_interface="fi.w1.wpa_supplicant1"/>
>>>>>                 <allow receive_sender="fi.w1.wpa_supplicant1" 
>>>>> receive_type="signal"/>
>>>>>         </policy>
>>>>>         <policy context="default">
>>>>>                 <deny own="fi.epitest.hostap.WPASupplicant"/>
>>>>>                 <deny 
>>>>> send_destination="fi.epitest.hostap.WPASupplicant"/>
>>>>>                 <deny 
>>>>> send_interface="fi.epitest.hostap.WPASupplicant"/>
>>>>>
>>>>>                 <deny own="fi.w1.wpa_supplicant1"/>
>>>>>                 <deny send_destination="fi.w1.wpa_supplicant1"/>
>>>>>                 <deny send_interface="fi.w1.wpa_supplicant1"/>
>>>>>                 <deny receive_sender="fi.w1.wpa_supplicant1" 
>>>>> receive_type="signal"/>
>>>>>         </policy>
>>>>> </busconfig>
>>>> Do you think there is something wrong?
>>>>
>>>> Regards,
>>>>
>>>> Fabio
>>>>
>>>> Il 13/10/2016 12:10, Tomasz Bursztyka ha scritto:
>>>>> Hi Fabio,
>>>>>
>>>>>> I've found an important clue. If launching connmand in foreground 
>>>>>> (connmand -d -n) I see the following debug log:
>>>>>>
>>>>>>> connmand[1769]: 
>>>>>>> /home/user/Project/ICU/BUILD_YOCTO/build_lam_icu_systemd/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/connman/1.28-r0/connman-1.28/src/technology.c:technology_get()*No
>>>>>>>  
>>>>>>> matching drivers found for wifi*.
>>>>>> What's the meaning of this message? Why connmand can't find wifi 
>>>>>> drivers?
>>>>>
>>>>> This is about connman's driver: plugins/wifi.c along with gsupplicant
>>>>> And that can happen if wpa_supplicant dbus service is not found.
>>>>>
>>>>> Try:
>>>>> stop wpa_supplicant, and connman.
>>>>>
>>>>> in a terminal start wpa_supplicant un foreground with -u -ddd
>>>>>
>>>>> in another terminal start connman in foreground as you did.
>>>>>
>>>>> See if wpa_supplicant gets contacted. Something tells me it is not.
>>>>>
>>>>> If that's the case: then it's most likely a dbus config issue for 
>>>>> wpa_supplicant.
>>>>> Check /etc/dbus-1/system.d/wpa_supplicant.conf
>>>>>
>>>>> Tomasz
>>>>
>>>> -- 
>>>>
>>>> *Fabio Emiliani*
>>>>
>>>> */Software Engineer/*
>>>>
>>>> /Ph. +39 075 8298 532/
>>>>
>>>> /fabioemili...@artgroup-spa.com/ 
>>>> <mailto:fabioemili...@artgroup-spa.com>
>>>>
>>>> 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///
>>>>
>>>> /Ph. +39 075 8298 501 ? Fax +39 075 8298 525 /
>>>>
>>>> P*Please consider our environment before printing this e-mail***
>>>>
>>>
>>
>> -- 
>>
>> *Fabio Emiliani*
>>
>> */Software Engineer/*
>>
>> /Ph. +39 075 8298 532/
>>
>> /fabioemili...@artgroup-spa.com/ <mailto:fabioemili...@artgroup-spa.com>
>>
>> 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///
>>
>> /Ph. +39 075 8298 501 ? Fax +39 075 8298 525 /
>>
>> P*Please consider our environment  before printing this e-mail***
>>
>

-- 

*Fabio Emiliani*

*/Software Engineer/*

/Ph. +39 075 8298 532/

/fabioemili...@artgroup-spa.com/ <mailto:fabioemili...@artgroup-spa.com>

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***

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.01.org/pipermail/connman/attachments/20161013/51cf90ab/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo_ART_firma-1.jpg
Type: image/jpeg
Size: 16420 bytes
Desc: not available
URL: 
<http://lists.01.org/pipermail/connman/attachments/20161013/51cf90ab/attachment.jpg>

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

Subject: Digest Footer

_______________________________________________
connman mailing list
connman@lists.01.org
https://lists.01.org/mailman/listinfo/connman


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

End of connman Digest, Vol 12, Issue 17
***************************************

Reply via email to