You are not logged in.
I have invoked systemd-networkd. But when I start NetworkManager, the ip address is lost and the connections (both wired and wireless) displayed on NetworkManager try to connect for a while then automatically closed. It seems there are some conflicts. I want to use NetworkManager because within Gnome Desktop environment, it is convenient to manager network connections. Have anyone ever encountered this problem?
Last edited by archzhengwei (2014-07-14 02:57:07)
Offline
You can't have systemd-networkd and NetworkManager working at the same time.
Offline
@cris9288, I have them both working at the moment
@archzhengwei,I my case, 'systemd-networkd' is only started for systemd-timesync and not configured, maybe that helps you.
Offline
Thanks a lot @ qinohe, I didn't configure 'systemd-networkd', either but the problem still exists. BTW, may 'dhcpcd' and 'systemd-networkd' conflict?
Last edited by archzhengwei (2014-07-13 02:13:39)
Offline
Aha, I have found that actually 'dhcpcd' and 'NetworkManager' conflicts indeed, having nothing to do with 'systemd-networkd'. If you stop and disable 'dhcpcd', everything goes well.
Offline
@cris9288, I have them both working at the moment
@archzhengwei,I my case, 'systemd-networkd' is only started for systemd-timesync and not configured, maybe that helps you.
Interesting. Usually multiple network services will prevent each other from working, but it sounds like systemd-networkd serves other purposes. Good to know!
Offline
@archzhengwei, Good you figured it out, NetworkManager is still able to DHCP, even with the service (daemon) disabled.
I you are currently happy with it, don't forget to mark your post [Solved], thanks.
@chris9288, Well yes, in this case, I don't know about other cases, I didn't dive very deep into the systemd-network matter
Offline