6700 2014-09-09 09:45:08 +0000 systemd's resolved conflicts with connman 2017-04-06 02:37:35 +0000 1 1 7 Build System, Metadata & Runtime OE-Core connectivity 1.7 All Multiple RESOLVED WORKSFORME Medium enhancement 2.3 M4 1 ross.burton Qi.Chen meta.mr.watcher meta.watcher net147 --- --- No (bug/feature does not impact docs) oldest_to_newest 45482 0 ross.burton 2014-09-09 09:45:08 +0000 There have been reports that resolved and connman don't play nicely and you end up unable to resolve hostname. 45483 1 ross.burton 2014-09-09 09:45:41 +0000 Note that there's a patch due to be merged to disable resolved/networkd, so you'll need to re-enable them before testing. 48759 2 cristian.iorga 2015-02-12 14:19:10 +0000 Patch to disable resolved and networkd integrated: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ecb4014c58bfcffc0ace20db338bced54775b815 . 64424 3 ross.burton 2016-07-25 21:00:22 +0000 Reassigning to Chen as he's the systemd maintainer. Currently in oe-core we've "solved" this by disabling networkd and resolved in systemd. This clearly isn't optimal, especially for situations where networkd is preferable to connmand (such as containers or servers). We need to make networkd and resolved work when they are enabled if connmand isn't also installed, and somehow ensure that they're mutually exclusive. 71887 4 Qi.Chen 2017-03-30 02:33:14 +0000 I just did some tests. 1) systemd + resolved 2) systemd + connman 3) systemd + resolved + connman In the above three cases, I didn't see any problem. I'm going to close this bug if there's no objection. Regards, Chen Qi 72120 5 Qi.Chen 2017-04-06 02:37:35 +0000 Close this bug as stated in the above comment.