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#11231 - DHCP defaults/fails and then dhcpcd will not re-run unless a reboot is issued.

Attached to Project: Arch Linux
Opened by jasin (rooloo) - Saturday, 16 August 2008, 12:53 GMT
Last edited by Ronald van Haren (pressh) - Thursday, 16 October 2008, 16:58 GMT
Task Type Bug Report
Category Installation
Status Closed
Assigned To Simo Leone (neotuli)
Aaron Griffin (phrakture)
Architecture All
Severity Medium
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: DHCP will try to configure a network connection during the install when asked, But for some reason if this task fails, dhcp will assign a weird IP address and then tell the user the operation was Successful. But, this is where things get kinda weird. Because DHCP did not connect correctly nothing else will work and if you try to use dhcp again to reconfigure the network, you will recieve a message that says "dhcpcd can not be intialized" or something to that effect. Only way around this is to reboot and hope dhcp works next time.


Additional info:
* package version - 2008.06 ISO FTP install

Steps to reproduce: Unplug your ethernet from modem and boot into ftp install and try using dhcp multiple time to get an assigned IP address.

#1 Should not DHCP work multiple times? for instance a module was not loaded. Modprobe <module> and re-issue DHCP for a second time.

#2 DHCP should return the results of it's probe to the user so he/she can see if the network was properly configured. Not assume the network was configured successful just because DHCP gave it a weird DEFAULT ip address.
This task depends upon

Closed by  Ronald van Haren (pressh)
Thursday, 16 October 2008, 16:58 GMT
Reason for closing:  Implemented
Additional comments about closing:  should be fixed. current dhcpcd used the -L flag (no zeroconf)
Comment by jasin (rooloo) - Saturday, 16 August 2008, 12:54 GMT
http://bbs.archlinux.org/viewtopic.php?pid=407625#p407625

here is a link to the thread where the discussion first took place.
Comment by Gerhard Brauer (GerBra) - Saturday, 16 August 2008, 13:15 GMT
From my view this is a normal behavior. Also the man page says the same:
Local Link configuration
If dhcpcd failed to obtain a lease, it will probe for a valid IPv4LL
address (aka Zeroconf, aka APIPA). Once obtained it will probe every 10
seconds for a DHCP server to get a proper address.

If your network doesn't work like expected than a look at ifconfig/route shows the reason.

The reason that you could not start several dhcp clients on the same device is also clear from above man page text.
It must be stopped before starting a new (-k)

Me thinks also that the fact: dhcpcd return always 0/succed could be disconcerting.
For myself i always use parameter -L/−‐noipv4ll. I have no zeroconf networks.
Maybe this could be set also in the dhcdcd.conf on install cd.

Loading...