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. Regards Marcel _______________________________________________ connman mailing list [email protected] https://lists.moblin.org/mailman/listinfo/connman
