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#7715 - dhcpcd 3.1.1-1 broken

Attached to Project: Arch Linux
Opened by Christoph Neuroth (delmonico) - Tuesday, 31 July 2007, 09:04 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 01 August 2007, 21:11 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Since upgrading dhcpcd the program sets a wrong IP address and no routing entries. Additionally, it produces a timeout error. All non-arch machines in the network set correct information, so the router seems to send the correct values...

Additional info:
[2007-07-31 01:11] upgraded dhcpcd (3.0.17-1 -> 3.1.1-1)

Steps to reproduce:
Run dhcpcd, see a messed up network config ;)
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Wednesday, 01 August 2007, 21:11 GMT
Reason for closing:  Fixed
Comment by Michal Bozon (mykhal) - Tuesday, 31 July 2007, 14:58 GMT
I have the same problem. I think severity is higher than "low".
Comment by Michal Bozon (mykhal) - Tuesday, 31 July 2007, 15:05 GMT
dhcpcd seem to send invalid requests. It is not visible in "dhcpcd -d eth0" output, but in the dhcp server log, MAC address is prepended by some additional numbers.
Comment by Michal Bozon (mykhal) - Tuesday, 31 July 2007, 15:43 GMT
additional note: this bugreport is initiated by dhcpcd package maintainer, so I don't understand why this new buggy version is in Current..
Comment by Tobias Powalowski (tpowa) - Tuesday, 31 July 2007, 19:33 GMT
i cannot confirm here all is fine by running dhcpcd here, please tra new 3.1.3.
thanks
Comment by Roman Kyrylych (Romashka) - Wednesday, 01 August 2007, 08:48 GMT
re-opened on this request:
I have found the reason of the buggy behavior (in my case). It sends DUID (it has maybe something to do with ipv6) in the request, and it is new in 3.1 version. The DUID is prepended to the MAC, or so, and some dhcp servers do not understand it. Please look in the INSTALL of the dhcpcd source, there is mention (and almost only this mention) about ENABLE_DUID, it should be considered.
Comment by Matt Runion (mrunion) - Wednesday, 01 August 2007, 14:32 GMT
I upgraded dhcpcd to 3.1.1 (from 3.0.19) a day or two ago and ever since the upgrade I am getting my "/var/log/everything.log" filled up with this:

...
Jul 31 08:26:25 plunkerbunkey dhcpcd[4845]: eth0: broadcasting for a lease
Jul 31 08:26:55 plunkerbunkey dhcpcd[4845]: eth0: timed out
Jul 31 08:26:55 plunkerbunkey dhcpcd[4845]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.info'
Jul 31 08:26:55 plunkerbunkey dhcpcd[4845]: eth0: checking 169.254.40.121 is available on attached networks
Jul 31 08:26:56 plunkerbunkey dhcpcd[4845]: eth0: adding IP address 169.254.40.121/16
...

This happens over and over and over. I tried changing the line in rc.conf for INTERFACES to read:

...
INTERFACES=(lo !eth0 eth1)
...

but it didn't stop the messages.

Here is the pertinent section of my rc.conf:

...
lo="lo 127.0.0.1"

#---- Wired (LAN)
eth0="dhcp"
eth1="dhcp"

#---- Wireless (eth1)
wlan_eth1="eth1 essid NotForGeneralUse"

WLAN_INTERFACES=(eth1)
INTERFACES=(lo eth0 eth1)
...

This is a laptop and has both wired (eth0) and wireless (eth1) LAN cards. I only use the wireless because I still have not had to connect to a wired connection. I tried both dhcpcd 3.1.1 and 3.1.3 and this occurs. The messages repeat about ever 30-40 seconds and the log just fills up with them. If I go back to dhcpcd 3.0.19 the messages stop.

Does this help with anything?
Comment by Tobias Powalowski (tpowa) - Wednesday, 01 August 2007, 20:12 GMT
please try new 3.1.3-2 i disabled DUID now.
Comment by Michal Bozon (mykhal) - Wednesday, 01 August 2007, 20:24 GMT
I am pretty sure it will fix the DUID issue. But what if someone needs DUIDs ? When using dhcpcd option -I "", it does not include DUID in the DHCP request at all. I propose to do not disable DUID at compile time, but add the -I "" option into the config, to be able to enable DUIDs later. Unfortunately, there are some problems with the empty string in config.. look at http://bbs.archlinux.org/viewtopic.php?pid=269942#p269942 I could not get it work automatically
Comment by Tobias Powalowski (tpowa) - Wednesday, 01 August 2007, 21:11 GMT
atm it is fixed when we need duids then we can think of this solution

Loading...