Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#30929 - [initscripts] network script starts dhcpcd on all interfaces without configuration

Attached to Project: Arch Linux
Opened by Gary (smoothgrips) - Monday, 30 July 2012, 20:28 GMT
Last edited by Tom Gundersen (tomegun) - Tuesday, 14 August 2012, 21:22 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tom Gundersen (tomegun)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

After upgrading from dnsutils-9.9.1.P1-1 to dnsutils-9.9.1.P2-1, networkmanager fails to receive a dhcp lease. This happens for both wired connections and wireless connections. The following is emitted repeatedly in the log:

NetworkManager[12192]: <info> Activation (eth0) starting connection 'Wired connection 1'
NetworkManager[12192]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[12192]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[12192]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[12192]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager[12192]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[12192]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
NetworkManager[12192]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[12192]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
NetworkManager[12192]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
NetworkManager[12192]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
NetworkManager[12192]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
NetworkManager[12192]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
NetworkManager[12192]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
NetworkManager[12192]: <info> dhcpcd started with pid 12287
NetworkManager[12192]: <info> Activation (eth0) Beginning IP6 addrconf.
NetworkManager[12192]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
dhcpcd[12287]: sending commands to master dhcpcd process
dhcpcd[536]: control command: /sbin/dhcpcd -B -K -L -G -c /usr/lib/networkmanager/nm-dhcp-client.action eth0
NetworkManager[12192]: <info> (eth0): DHCPv4 client pid 12287 exited with status 0
NetworkManager[12192]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
NetworkManager[12192]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) started...
NetworkManager[12192]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
kernel: [17295.761671] eth0: no IPv6 routers present
NetworkManager[12192]: <info> (eth0): IP6 addrconf timed out or failed.
NetworkManager[12192]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
NetworkManager[12192]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
NetworkManager[12192]: <info> (eth0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
NetworkManager[12192]: <info> Marking connection 'Wired connection 1' invalid.
NetworkManager[12192]: <warn> Activation (eth0) failed.
NetworkManager[12192]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
NetworkManager[12192]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
NetworkManager[12192]: <info> (eth0): deactivating device (reason 'none') [0]

networkmanager does this indefinitely until stopped.

lspci:
Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)

networkmanager version 0.9.4.0-6
kernel version: 3.4.7-1 (also happens with 3.4.6-1)
This task depends upon

Closed by  Tom Gundersen (tomegun)
Tuesday, 14 August 2012, 21:22 GMT
Reason for closing:  Not a bug
Comment by Jeff Cook (cookiecaper) - Monday, 30 July 2012, 21:02 GMT
While dnsutils 9.9.1.P2-1 + networkmanager 0.9.4.0-6 works well on my machine, I too have seen it fail in this manner. In my experience, netcfg functions fine, while NetworkManager loops connection initalization, unsuccessfully trying to get a DHCP lease, until it is manually disrupted.

For those having issues, remember to fully kill any lingering dhcpcd daemons after downgrading. A full reboot should suffice.
Comment by Luke Crooks (Crooksey) - Tuesday, 31 July 2012, 07:47 GMT
This also happens to me, no networking facilities at all with network manager.

EDIT: I still had the "network" daemon listed in my rc.conf, this worked fine before the update, but the update caused this to crash network manager, disabling it should solve your problem. The wiki documentation is up to date.
Comment by Jan de Groot (JGC) - Wednesday, 01 August 2012, 18:30 GMT
Recent initscripts have changed behaviour a bit I guess. When you launch the "network" daemon without any network configuration, somehow this launches dhcpcd on all interfaces. When networkmanager tries to put up a connection, it can't get a dhcp lease because of this and returns instantly with a timeout.
Comment by Tom Gundersen (tomegun) - Sunday, 05 August 2012, 23:01 GMT
This was intentional.

Using more than one daemon to manage your network will clearly not work well (unless you are careful). Either use 'networkmanager' or 'network'. Not both.

Earlier this configuration would simply lead to an error printed at boot and the network daemon failing. That was not very useful, so now we start dhcpcd on all interfaces. If you want it to be only started on a particular one then specify that in rc.conf (or if you want none at all, then you can disable the daemon).

I guess what I'm saying is: what behavior would you expect? What is the usecase?
Comment by Jan de Groot (JGC) - Monday, 06 August 2012, 07:11 GMT
I think most setups that use networkmanager but have the network daemon in there, are the ones that used the network daemon to start the localhost interface. As initscripts does that from rc.sysinit now, it makes no sense to use the network daemon anymore.

Loading...