>-----Original Message----- >From: [email protected] >[mailto:[email protected]] On Behalf Of Marcel Holtmann >Sent: Tuesday, May 26, 2009 9:17 PM >To: [email protected] >Subject: Re: [connman] How to map the service to the device? > >Hi Jackie, > >> Currenly the service api provides the details states of a >connection. But I found there is no way to identify which >device provides the service, especially when there are two >interfaces with same type. For example, I tried with two >ethernet interfaces. One is built-in and another is usb >ethernet dongle. Then through service interface, I could get >notification of an ethernet service state changes. Then I >would get more information of the device that provide the >service. But I could not identify which device is for that >service. Did I miss anything? >> >> I found the object path for services and any other D-Bus >interfaces include the MAC address of the device, which can be >used to identify the relation between services and devices. >But I think that may not the way you designed in API level to >map the service and device? > >so we can add a Device property to the service object to identify the >device that it uses. > >However why do you think this is needed? What does mapping devices to >services help us at all. > Actually I'm doing a Connman Setting program with D-Bus interfaces provided by Connman. I need to monitor details state (idle/association/configuration/ready...) changes of all interfaces during their connection setup. Those states are only provided by service apis.
Besides to that, I can also think out a senario for normal usage with two ethernet connections. For example, when I use two ethernet interface simultaneous. One connect to company network for normal email and another connect a local test network for dev purpose. Then I want to disconnect or reconnect/reconfigure the local test network by using the GUI, which probably shows both ethernet network icons and update the state changes. But I don't know which one is for the local network. For WiFi, probably it's not problem since the network apis expose the device so I could know which device connect to which network. But it also have problem to track the status changes through service api. When I get a "configuration" state notification, I can not know which network is in that state? Maybe the "Name" property can map wifi service to wifi network but sometime the "Name" are NULL or same for some cases and can not be used as a unique identity. Maybe above cases rarely happen. But I think to add a Device property seems not harmful and provide more flexibility and necessary information to the Connman Setting/GUI development. :) I found another problem of carrick-connection-panel on Moblin when support two ethernets interfaces. I plugged in another USB dongle ethernet card but the carrick will not show two ethernet networks but only one "ethernet". Looks like the ethernet has no Networks properties. I think we probably can also add the interface name "eth0" as the Name of the network. So the Connman provides enough information and the Connman Setting/GUI program can decide how to show them to end user. If only one ethernet interface, the GUI will just show "ethernet" like existing one but not show the "eth0" which is not understood by user. If there are more than one, the GUI can show more informaion the eth0 and eth1. Thanks Jackie >Regards > >Marcel > > >_______________________________________________ >connman mailing list >[email protected] >https://lists.moblin.org/mailman/listinfo/connman > _______________________________________________ connman mailing list [email protected] https://lists.moblin.org/mailman/listinfo/connman
