FS#68515 - netctl not getting IPv4 address after dhcpcd upgrading to 9.3.1-1
Attached to Project:
Arch Linux
Opened by QIAN CHEN (elgs) - Tuesday, 03 November 2020, 12:28 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 28 November 2020, 15:03 GMT
Opened by QIAN CHEN (elgs) - Tuesday, 03 November 2020, 12:28 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 28 November 2020, 15:03 GMT
|
Details
Description:
After dhcpcd upgrading to 9.3.1-1, netctl is no longer getting IPv4 address from my home router. IPv6 is not not affected. Downgrading to dhcpcd-9.2.0-1 solves the problem. This happened on Raspberry Pi 4 (ARM7) and Raspberry Pi 0 (ARM 6). I don't have an x86_64 in hand, so I didn't test it on x86_64. Good version: dhcpcd-9.2.0-1 Bad version: dhcpcd-9.3.1-1 Additional info: * package version(s) dhcpcd-9.3.1-1 * config and/or log files etc. Description='A simple WPA encrypted wireless connection' Interface=wlan0 Connection=wireless Security=wpa IP=dhcp ESSID='NETGEAR69' # Prepend hexadecimal keys with \" # If your key starts with ", write it as '""<key>"' # See also: the section on special quoting rules in netctl.profile(5) Key='ArchLinux' # Uncomment this if your ssid is hidden #Hidden=yes # Set a priority for automatic profile selection #Priority=10 * link to upstream bug report, if any Steps to reproduce: After dhcpcd upgrading to 9.3.1-1, netctl is no longer getting IPv4 address from my home router. IPv6 is not not affected. Downgrading to dhcpcd-9.2.0-1 solves the problem. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Saturday, 28 November 2020, 15:03 GMT
Reason for closing: None
Additional comments about closing: This is the Arch bug tracker. Arch doesn't run on ARM.
Saturday, 28 November 2020, 15:03 GMT
Reason for closing: None
Additional comments about closing: This is the Arch bug tracker. Arch doesn't run on ARM.
Edit: downgrading dhcpcd is not resolving the issue from
FS#68514In case, that this is a pressing issue for anyone: dhclient turned out to work fine for me under netctl - so I recommend to switch to that.
regards,
deepthought
FS#68514ticket: switching to netctl/dhclient is a fix/workaround for this issue`uname -a`: `Linux archlinux-build 5.9.10-arch1-1 #1 SMP PREEMPT Sun, 22 Nov 2020 14:16:59 +0000 x86_64 GNU/Linux`.
Untested on Arch Linux ARM/32; This is from a standard 64-bit Arch Linux perspective.
FS#68514ticket: switching to netctl/dhclient is a fix/workaround for this issueI don't see a mention of that in the other ticket, which seemingly has nothing at all to do with this ticket (systemd-networkd vs netctl+dhcpcd).
# uname -a
Linux arch 5.9.10-arch1-1 #1 SMP PREEMPT Sun, 22 Nov 2020 14:16:59 +0000 x86_64 GNU/Linux
EDIT:
and yes, mentioning the systemd-networkd issued (not getting ipv4 with this setup) has nothing to do with netctl+dhcpcd, sorry for that
Sadly SECCOMP implementation is very platform dependent.
I can confirm that dhcpcd-9.3.3 had patches specifically for ARM32.