Hi,
On Tue, 2015-02-24 at 17:59 +0200, Mihai Neagu wrote:
> >> If you are using Ethernet, then both interfaces should be configured.
> >> In general, the plugged in cable aka carrier for Ethernet was support
> >> to indicate that it gets used. Of course only one can have the default
> >> route of course.
> > The current feature is that all ethernet interfaces are treated in the
> > very same manner as every other service; if there already is another
> > service connected, the newly connected ethernet will not be connected
> > either. This is a matter of defining a detailed expectation of ethernet
> > network behavior plus a small amount of fixing.
>
> Currently we support auto-connection to all interfaces (wired, wifi and
> gadget) that have carrier, and connecting to just one at a time would
> mean a regression in the network stack abilities. Our devices may need
> to be connected to several networks at the same time, each one having a
> different purpose.In this case,the metric would have various values for
> different entries in the routing table.
After re-reading ConnMan documentation, not connecting an ethernet
network that was plugged in is to be considered a bug. The action of a
cable plug-in is documented in the description of the Connect() method
call in doc/service-api.txt as "...the plugging of a cable will trigger
connecting automatically...". This on the initial cable plug-in, it is
possible to disconnect and connect ethernet services via D-Bus later on.
I'll fix this in the near future.
Cheers,
Patrik
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
