On Mon, Feb 03, 2020 at 04:53:50PM +0300, Sergey Organov wrote:
Thanks! I've read it already, but it seemed unnatural to me to be
to parse/edit configuration file(s) directly, effectively duplicating
what connmand does anyway, especially as my actual aim is to do it from
The reason why the provisioning is done only by file is that the D-Bus
API lacks a way to create non existing services. You can only modify
currently available services via D-Bus.
I'll obviously do it, as it happens to be the only available way,
it's still unclear how does provisioning interoperate with configuration
through D-Bus/connmanctl? My quick test shows that "connmanctl
configure" starts to give (rather undescriptive) errors on provisioned
# connmanctl config ethernet_0018d7677f91_cable ipv4 dhcp
Error ethernet_0018d7677f91_cable: Not supported
connmanctl config ethernet_0018d7677f91_cable --ipv4 dhcp
effectively making provisioning and "connmanctl configure"
exclusive. Is it how it's designed to behave indeed?
Yes indeed, they are mutually exclusive due it's original use case.