On Tue, Sep 15, 2015 at 1:04 PM, Patrik Flykt <patrik.fl...@linux.intel.com>
wrote:
>
> Hi,
>
> On Tue, 2015-09-15 at 09:30 +0200, laurent vaudoit wrote:
>
> > in order to identify the network, is there some rules to apply?
> > Is it possible to use the format:
> > ethernet_MACADRESS_switchPORTNB_cable with PORTNB the dsa port number on
> > the switch?
>
> If this behavior is generic enough, maybe a '_p<id>_cable' should be
> used. Also check the port range, i.e. is %03x a suitable value or not. I
> suppose it is possible to create VLANs for this interface also, which
> means that the identifier needs to be built step by step taking also the
> VLAN information into account. Instead of an ioctl, is this information
> available in a newlink message? If so, that one should be used to avoid
> the extra ioctl.
>
ok, in case a vlan is created on this interface,
service name will be _p<id>_<vid>_cable
and if it is not a vlan, service name will be _p>id>_cable.
For the port range, i don't know many component, but a %02x should be
enough.
for newlink message, i'm not a specilaist of this but i did not found the
information in it, that's the reason i used ioctl.
>
> While we are at it, you have looked at systemd-networkd also, but
> noticed that you actually do need ConnMan because it also supports
> Bluetooth and WiFi?
>
Yes we need wifi, bluetooth, ethernet, ofono, and thats why we choose
connman
>
> Cheers,
>
> Patrik
>
Regards
Laurent
>
> _______________________________________________
> connman mailing list
> connman@connman.net
> https://lists.connman.net/mailman/listinfo/connman
>
_______________________________________________
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman
