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#57626 - [dhcpcd] 7.0.1-1 does not honor offered addresses

Attached to Project: Arch Linux
Opened by brent saner (sanerb) - Saturday, 24 February 2018, 23:59 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 26 February 2018, 14:50 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

Details

Description:
upon updating dhcpcd to 7.0.1-1, it seems to no longer accept and honor the offered address from the DHCP server. as such, static leases break.

upon switching the relevant netctl profile to DHCPClient='dhclient', i do indeed receive my expected static lease.

(DHCP server in this case is an Actiontec MI424WR-GEN3I, firmware version 40.21.24. I have not tested with other implementations.)

Note: the same static lease was working fine with previous versions of dhcpcd.
This task depends upon

Comment by Doug Newgard (Scimmia) - Monday, 26 February 2018, 14:49 GMT Comment by brent saner (sanerb) - Monday, 26 February 2018, 15:03 GMT
I saw that come in on the mailing lists as well but it seems to be unrelated; this network I noticed the behaviour on is fully IPv4 stack.
Comment by Roy Marples (rsmarples) - Tuesday, 27 February 2018, 09:07 GMT
Can you show a dhcpcd log for this with debug enabled please? Add this to /etc/dhcpcd.conf

debug
logfile /var/log/dhcpcd.log

Restart dhcpcd. Once an address is configured, attach the log file here please.
Comment by dummys (dummys) - Tuesday, 27 February 2018, 22:45 GMT
same problem here with package: dhcpcd-7.0.1-1-x86_64, with downgrading to dhcpcd-6.11.5-1-x86_64 working again. Here is my debug log:

Feb 27 23:40:53 [5233]: dhcpcd-7.0.1 starting
Feb 27 23:40:53 [5233]: wlan0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
Feb 27 23:40:53 [5233]: wlan0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
Feb 27 23:40:53 [5233]: DUID 00:01:00:01:22:28:79:46:9c:b6:d0:d1:3b:07
Feb 27 23:40:53 [5233]: wlan0: IAID d0:d1:3b:07
Feb 27 23:40:53 [5233]: wlan0: delaying IPv6 router solicitation for 0.1 seconds
Feb 27 23:40:53 [5233]: wlan0: delaying IPv4 for 0.6 seconds
Feb 27 23:40:53 [5233]: wlan0: soliciting an IPv6 router
Feb 27 23:40:53 [5233]: wlan0: sending Router Solicitation
Feb 27 23:40:54 [5233]: wlan0: soliciting a DHCP lease
Feb 27 23:40:54 [5233]: wlan0: sending DISCOVER (xid 0x157053fd), next in 4.0 seconds
Feb 27 23:40:54 [5233]: wlan0: NAK: from 192.168.2.254
Feb 27 23:40:54 [5233]: wlan0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NAK
Feb 27 23:40:54 [5233]: wlan0: soliciting a DHCP lease
Feb 27 23:40:54 [5233]: wlan0: sending DISCOVER (xid 0x65d42a29), next in 4.3 seconds
Feb 27 23:40:54 [5233]: wlan0: NAK: from 192.168.2.254
Feb 27 23:40:54 [5233]: wlan0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NAK
Feb 27 23:40:55 [5233]: wlan0: soliciting a DHCP lease
Feb 27 23:40:55 [5233]: wlan0: sending DISCOVER (xid 0x9fa7ab38), next in 3.6 seconds
Feb 27 23:40:55 [5233]: wlan0: NAK: from 192.168.2.254
Feb 27 23:40:55 [5233]: wlan0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NAK
Feb 27 23:40:57 [5233]: wlan0: soliciting a DHCP lease
Feb 27 23:40:57 [5233]: wlan0: sending DISCOVER (xid 0x880fd221), next in 3.5 seconds
Feb 27 23:40:57 [5233]: wlan0: NAK: from 192.168.2.254
Feb 27 23:40:57 [5233]: wlan0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NAK
Feb 27 23:40:57 [5233]: wlan0: sending Router Solicitation
Feb 27 23:40:59 [5233]: received SIGINT, stopping
Feb 27 23:40:59 [5233]: wlan0: removing interface
Feb 27 23:40:59 [5233]: wlan0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' STOPPED
Feb 27 23:40:59 [5233]: dhcpcd exited
Comment by Roy Marples (rsmarples) - Tuesday, 27 March 2018, 06:46 GMT
Sorry for not spotting this reply sooner (no email notificiaton?)

So you're getting a NAK after sending a DISCOVER?
Sounds like a faulty DHCP server.

Could you get a full tcpdump of the transaction that can be viewed in wireshark please?
Also, the same log from dhcpcd-6 would be useful.

Comment by dummys (dummys) - Tuesday, 27 March 2018, 11:56 GMT
Hi, the log I showed you is from dhcpcd. I will do the wireshark stuff tonight

Loading...