Hi,
On Mon, 2014-10-27 at 14:33 -0500, Ryan Kuester wrote:
> On Mon, Oct 27, 2014 at 05:07:34PM +0200, Jukka Rissanen wrote:
> > On ma, 2014-10-27 at 09:44 -0500, Ryan Kuester wrote:
> > > Hi all,
> > >
> > > There's a thread[1] from early 2013 which concluded that the way to
> > > statically configure wired Ethernet interfaces that are not connected is
> > > by writing .config files to /var/lib/connman/. In my case, this seems to
> > > require:
The other option is of course to have another app or startup script to
connect all ethernet services via D-Bus. Depends on the use case what
the best solution is.
> > You should use the ConnMan dbus API to get the configuration in a UI.
> > The provisioned services are almost identical to normal services, only
> > difference is that the provisioned ones have immutable flag set which
> > means that you can edit only minimal subset of service properties.
>
> Thanks for the reply, Jukka. I'd prefer to read configuration using the
> API as you suggest, but are there D-Bus objects representing
> disconnected Ethernet interfaces? It didn't look that way to me.
There are D-Bus objects only for services that can be used. In order to
be used, an ethernet interface needs a cable plugged in.
The idea behind .config provisioning is that all information needed for
the service already exists, is delivered out-of-band to the device and
is provably correct. Therefore provisioned information is set to
immutable, as there isn't any network information that need to be
modified. The D-Bus API covers for the default situation where there are
services that the user him/herself wants to configure.
Cheers,
Patrik
_______________________________________________
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman
