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#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
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

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.
Comment by Thomas Jäger (xunil64) - Sunday, 08 November 2020, 08:40 GMT
I have a similiar issue, see https://bugs.archlinux.org/task/68514 - i will check if downgrading dhcpcd will solve the issue

Edit: downgrading dhcpcd is not resolving the issue from FS#68514
Comment by Erich Eckner (deepthought) - Thursday, 19 November 2020, 06:57 GMT
I saw the same happen on other flavours of arch (namely archlinux arm and archlinux32): not getting ipv4 addresses with dhcpcd under netctl. I cannot comment on the precise versions of dhcpcd, though.

In 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
Comment by Thomas Jäger (xunil64) - Thursday, 19 November 2020, 09:12 GMT
As mentioned in the related FS#68514 ticket: switching to netctl/dhclient is a fix/workaround for this issue
Comment by Kevin Morris (kevr) - Wednesday, 25 November 2020, 12:18 GMT
This works fine on one of my systems with ethernet with `netctl 1.23-1` and `dhcpcd 9.3.1-1`. dhcpcd retrieves an IPv4 address like I'd expect.

`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.
Comment by Kevin Morris (kevr) - Wednesday, 25 November 2020, 16:58 GMT
> As mentioned in the related FS#68514 ticket: switching to netctl/dhclient is a fix/workaround for this issue

I 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).
Comment by Thomas Jäger (xunil64) - Wednesday, 25 November 2020, 18:00 GMT
tested netctl with dhclient and dhcpcd (9.3.3) - with both methods i will get an ipv4 address

# 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

Comment by Kevin Morris (kevr) - Wednesday, 25 November 2020, 18:29 GMT
Close request note: Apologies, I got confused thinking xunil64 was OP of this post -- OP has not replied and mentioned that 9.3.3-1 fixes it, yet.
Comment by Roy Marples (rsmarples) - Saturday, 28 November 2020, 14:59 GMT
dhcpcd-9.3.0 enabled SECCOMP for privsep on Linux.
Sadly SECCOMP implementation is very platform dependent.
I can confirm that dhcpcd-9.3.3 had patches specifically for ARM32.

Loading...