| Summary: | net-misc/networkmanager-0.8.1-r3 fails to connect if net-misc/dhcpcd-5.2.7 was already started | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | denysonique <dennisonic> |
| Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | NetworkManager with dhcpcd running and after having killed it(dhcpcd) | ||
Created attachment 243533 [details]
NetworkManager with dhcpcd running and after having killed it(dhcpcd)
I have attached a log when attempting to connect with dhcpcd already started and successfully connecting after I kill the /sbin/dhcpcd process.
you cannot have multiple different tools trying to configure your network settings. If you're using NetworkManager, you cannot have dhcpcd running as a daemon. NetworkManager will spawn it over dbus with required options to configure your IP address. When dhcpcd is run as standalone daemon, it tries to take over network management, rather then provide DHCP address only. So to solve your issue, please run rc-update del dhcpcd I am having the same problem as the OP, but I do not have dhcpcd in any of the init runlevels so running `rc-update del dhcpcd` fails, but it still starts at startup. |
NetworkManager tries to get the IP but it fails as /sbin/dhcpcd is already running(started at boot time by /etc/init.d/dhcpcd). After killing the dhcpcd process NetworkManager successfully connects using /etc/sbin/dhcpcd.