Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. 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#66231 - [networkmanager] No IPv4 connectivity with NetworkManager since dhcpcd version 9.0.0-2

Attached to Project: Arch Linux
Opened by Ferdinand Bachmann (Ferdi265) - Sunday, 12 April 2020, 17:06 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 05 May 2020, 14:13 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:

After updating to dhcpcd 9.0.0-2 from 8.1.7-1, NetworkManager fails to lease an IPv4 address via DHCP.

relevant journal logs:

Apr 12 14:07:18 lenny NetworkManager[803]: <info> [1586693238.0959] policy: auto-activating connection 'DHCP Ethernet' (6d37eafb-68ac-3cf2-bbe2-30d0a38e4a94)
Apr 12 14:07:18 lenny NetworkManager[803]: <info> [1586693238.0964] device (enp3s0): Activation: starting connection 'DHCP Ethernet' (6d37eafb-68ac-3cf2-bbe2-30d0a38e4a94)
Apr 12 14:07:18 lenny NetworkManager[803]: <info> [1586693238.0966] device (enp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Apr 12 14:07:18 lenny NetworkManager[803]: <info> [1586693238.0970] manager: NetworkManager state is now CONNECTING
Apr 12 14:07:18 lenny NetworkManager[803]: <info> [1586693238.0973] device (enp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Apr 12 14:07:18 lenny NetworkManager[803]: <info> [1586693238.0980] device (enp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Apr 12 14:07:18 lenny NetworkManager[803]: <info> [1586693238.0987] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Apr 12 14:07:18 lenny NetworkManager[803]: <info> [1586693238.1005] dhcp4 (enp3s0): dhcpcd started with pid 856
Apr 12 14:07:18 lenny dhcpcd[856]: ps_init: /var/lib/dhcpcd/var/lib/dhcpcd: Operation not permitted
Apr 12 14:07:18 lenny NetworkManager[803]: <warn> [1586693238.1280] dhcp-listener: dhcp-event: didn't have associated interface.
Apr 12 14:07:18 lenny dhcpcd[862]: if_learnaddrs: if_addrflags6: ::1%lo: No such file or directory
Apr 12 14:07:18 lenny dhcpcd[862]: if_learnaddrs: if_addrflags6: fe80::f71f:b77d:3530:14d%enp3s0: No such file or directory
Apr 12 14:07:18 lenny NetworkManager[803]: <warn> [1586693238.1460] dhcp-listener: dhcp-event: (pid 862) unhandled DHCP event for interface enp3s0
Apr 12 14:07:18 lenny dhcpcd[862]: /var/lib/dhcpcd/duid: Permission denied
Apr 12 14:07:18 lenny dhcpcd[862]: DUID 00:03:00:01:54:ee:75:fe:7e:c9
Apr 12 14:07:18 lenny dhcpcd[862]: enp3s0: IAID 75:fe:7e:c9
Apr 12 14:07:19 lenny dhcpcd[862]: enp3s0: soliciting a DHCP lease
Apr 12 14:07:20 lenny dhcpcd[862]: enp3s0: leased 10.0.0.1 for 86400 seconds
Apr 12 14:07:20 lenny dhcpcd[862]: dhcp_bind: Permission denied
Apr 12 14:07:20 lenny dhcpcd[862]: enp3s0: adding route to 10.0.0.0/24
Apr 12 14:07:20 lenny NetworkManager[803]: <warn> [1586693240.9901] dhcp-listener: dhcp-event: (pid 862) unhandled DHCP event for interface enp3s0

Steps to reproduce:

I only ever observed this on my own machine with a regular default DHCP ethernet connection config. I didn't try this on a different machine yet.
Note: I removed irrelevant log entries from the wifi, which tried to connect in parallel. If needed I can set up a clean config and try to provide fresh logs.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Tuesday, 05 May 2020, 14:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  dhcpcd support has been disabled
Comment by Antonio Rojas (arojas) - Sunday, 12 April 2020, 17:17 GMT
NM doesn't support dhcpcd 9, see https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/410. The plugin will probably be disabled if nobody fixes it soon.
Comment by zoug (zoug) - Sunday, 26 April 2020, 19:23 GMT
*EDIT* I did not see the comment from arojas above, said the same

Loading...