Send connman mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."


Today's Topics:

   1. Providing service factory defaults ([email protected])


----------------------------------------------------------------------

Message: 1
Date: Fri, 4 Aug 2017 10:55:48 +0200
From: [email protected]
To: [email protected]
Subject: Providing service factory defaults
Message-ID:
        <[email protected]>
Content-Type: text/plain;charset=utf-8

Hi,

I work for a company that makes a "router"-like product with 2 ethernet
interfaces (WAN+LAN). When the product is shipped to customer, it is setup
with dhcp on WAN (eth0) and static IP on LAN (eth1).

The customer is free to reconfigure the network settings, the above is
just the factory default.

Today we use /etc/network/interfaces+ifup/ifdown to achieve this. It works
fine, but it's a hassle for the customer because they don't like editing
cryptic textfiles. We would like to migrate to connman and offer the
customer the ability to configure the device through a webinterface that
apply network changes through the connman DBUS API.

We've been able to get connman running and we can configure it through its
API, it's great. The issue we're facing now is how to setup factory
defaults. We've tried to provision services with configs, but as
provisioned services are immutable it does not fit our use-case.

One could write updates to the service config files since connman monitors
and reloads these, but then we might aswell continue using
/etc/network/interfaces since the whole point of migrating to connman was
to configure through the DBUS API.

Is there a way to provide a "factory default" for each Ethernet-interface,
without making the services immutable?




------------------------------

Subject: Digest Footer

_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman


------------------------------

End of connman Digest, Vol 22, Issue 2
**************************************

Reply via email to