On Fri, 2014-01-17 at 11:11 +0000, VanCutsem, Geoffroy wrote: > I'd recommend to use ConnMan directly for this instead of > modifying/creating config files
I think this is pretty much the only right way to do it. I am not an expert in the area at all, but let me share my understanding here, may be it helps Gorka to get started. May be it helps others to see the general picture too. In Tizen IVI we use connman. It is very different to the traditional networking managers we use in Desktop Linux like in Fedora. It does things differently. Many config files we are used to see in Desktop Linux do not exist or simply ignored by connman. One of the main design principles of connman is that it tries hard to configure everything automatically without requiring user input at all. It tries to discover everything dynamically and use sane defaults. If you have a standard network with a DHCP server, connman will take all the data from DHCP. Connman will discover whether the NTP server is available and configure and will bring NTP system up. All automatic, and transparent to the users. Some things like WiFi are disabled by default. Ethernet is enabled and gets configured automatically. BTW, connman is a daemon, the process name is connmand. At times when you need to use some special settings, say, use a static IP addresses. You may not have the DHCP server. Then you have to configure connman. Connmand has interfaces which can be used to change many settings. These interfaces are accessible via D-Bus. In the past there was no easy way to configure connmand from the shell prompt, because you cannot talk to D-Bus from the shell, usually :-) Nowadays there is the 'connmanctl' tool which can be used to configure many useful things. Including WiFi - just enable the WiFi technology support. Connmanctl does not support all the possible connman switches. If the one you need is missing, then you needs to talk to the connman community about this. There is a mailing list and an IRC channel. In the pase we did not have 'connmanctl', so we had to use various connman test scripts which could do useful things like enabling WiFi. The had different purpose, of course, but worked as command line tools sometimes. Nowadays we should use connmanctl. When you configure connman, it saves the configuration in its private config files. Those files are not for anyone to look at or change. They can be changed only by connman. We do not even need to know where they are. When you reboot, connman will read those files and configure the networking accordingly. There is one configuration file, though, which is meant to be used for provisioning. Nowadays you take the Tizen IVI image which has no connman configuration (but probably should?), and connman automatically creates it and saves auto-discovered data there on the first boot. What if you want WiFi on the first boot? This is where this provisioning configuration comes handy. You can loop-back mount your image, change it, unmount, flash, boot, and have it there. This is the documentation for the provisioning config file. https://review.tizen.org/git/?p=framework/connectivity/connman.git;a=blob;f=doc/config-format.txt;hb=HEAD There are various other docs in that folder https://review.tizen.org/git/?p=framework/connectivity/connman.git;a=tree;f=doc;hb=HEAD Now, the provisioning file may be missing some useful settings. Then you need to talk to the connman community about this. Hope this is helps. Thanks! -- Best Regards, Artem Bityutskiy _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
