Image location: http://autobuilder.yoctoproject.org/pub/nightly/20130122-2/ Tree/Branch: poky/master Git Rev: 8d6e55bf2192524bda84138b5356a2791adbbe61 Steps: 1. Launch connman-properties after system booting 2. choose "offline mode" and check the connection of all network interfaces There is no response when click the "OfflineMode" button. the network interfaces still connect.
This is probably because we're telling connman to ignore the statically configure networking channel.
Hi Yi, For qemu machines connman doesn't manage any ethX interface anymore, so all connman networking tests on qemu are irrelevant. Have a look at /etc/connman/main.conf: [General] NetworkInterfaceBlacklist = eth Commit 7048fbdc05c1f2d9acaf1052550dec792c1f18da introduced connman-conf recipe for all qemu machines, blacklisting eth interfaces. The reason behind the change was that on qemu machines the interface is statically configured anyway at boot time (runqemu passes an ip to qemu) and restarting connman would have killed the network (reconfiguring the interface). So, I'm not really sure how we should handle this, given that all connman tests on qemu are now irrelevant...
Hello, this situation is generated by a previous patch that I have introduced, meant to stop connman from messing up with qemu machines network configuration. As a side effect, wired interface (in this case eth0) are no longer under connman's control. A better fix is in the work. The situation is a little bit difficult because of connman's inability of providing ethernet provisioning.
In connman 1.12, Ethernet provisioning is introduced.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=6159ad1063f4be518d8f0a1c024f12fc16d13592
Verified with master branch: 4da406cd50cf02a63ed76810a670aba1eb561c79