FS#31388 - Running dhcpcd prevents network connections

Attached to Project: Arch Linux
Opened by Stanislaw Pitucha (viraptor) - Sunday, 02 September 2012, 11:57 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 12 September 2012, 17:03 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After booting up, NetworkManager fails to connect me to any network claiming:

Sep 2 12:47:19 gumby NetworkManager[420]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 2 12:47:19 gumby NetworkManager[420]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Sep 2 12:47:19 gumby NetworkManager[420]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Sep 2 12:47:19 gumby NetworkManager[420]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Sep 2 12:47:19 gumby NetworkManager[420]: <info> dhcpcd started with pid 5933
Sep 2 12:47:19 gumby NetworkManager[420]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Sep 2 12:47:19 gumby dhcpcd[5933]: sending commands to master dhcpcd process
Sep 2 12:47:19 gumby NetworkManager[420]: <info> (wlan0): DHCPv4 client pid 5933 exited with status 0
Sep 2 12:47:19 gumby NetworkManager[420]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Sep 2 12:47:19 gumby NetworkManager[420]: <info> Activation (wlan0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Sep 2 12:47:19 gumby NetworkManager[420]: <info> (wlan0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]

This happens only if dhcpcd is running globally in the system. As soon as I kill the default 'dhcpcd -q' process, NetworkManager connects without any issues and spawns its own '/sbin/dhcpcd -B -K -L -G -c /usr/lib/networkmanager/nm-dhcp-client.action wlan0'.

Additional info:
* extra/networkmanager 0.9.4.0-6
* core/dhcpcd 5.6.0-1


Steps to reproduce:
Boot, try to connect to a network using NetworkManager.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 12 September 2012, 17:03 GMT
Reason for closing:  Not a bug
Comment by Jan de Groot (JGC) - Sunday, 02 September 2012, 21:17 GMT
You shouldn't use multiple daemons for your network. Probably you still start the "network" service without any configuration. When no interfaces are configured, the network scripts starts dhcpcd on all available interfaces, which renders other programs like pppoe, netcfg and networkmanager useless.
Comment by Jelle van der Waa (jelly) - Sunday, 09 September 2012, 09:04 GMT
Any update from user?

Loading...