Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 481078 - mkinitrd dhclient fails to DHCP
Summary: mkinitrd dhclient fails to DHCP
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: K12LTSP F11Blocker, F11FinalBlocker
TreeView+ depends on / blocked
Reported: 2009-01-22 01:58 UTC by Warren Togami
Modified: 2009-02-03 10:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-02-03 10:49:32 UTC

Attachments (Terms of Use)

Description Warren Togami 2009-01-22 01:58:49 UTC

if (execl(DHCLIENT, DHCLIENT, "-4", "-1", "-n", NULL) == -1)
It seems that -4 is an invalid parameter, because dhclient 4.0.0 and 4.1.0 both print syntax help when you use it.

dhclient -v -1 -n eth0
[outputs the syntax help]

dhclient -v -1 -n
execve (/sbin/dhclient-script, ...): No such file or directory
No broadcast interfaces found - exiting.

Bringing up the eth0 interface manually before dhclient makes no apparent difference in dhclient's behavior.

dhclient -v -1 -n eth0
Sending on   Socket/fallback
receive_packet failed on eth0: Network is down
DHCPDISCOVER on eth0 to port 67 interval 5
send_packet: Network is down

ifconfig eth0 up
dhclient -v -1 -n eth0
[This works!  Although it complains about dhclient-script not existing.  nash segfaults during parsing its output though.]

1. /var/run should be created by mkinitrd.
2. -4 parameter to dhclient is invalid.  dhclient's man page is wrong, or bug?
3. eth0 should be brought up before dhclient?
4. dhcp-4.1.0 dhclient is broken in some way compared to 4.0.0?
5. nash segfaults because it cannot handle parsing the output of dhclient's output.  (Or maybe the output of dhcp 4.0.0 is different from 4.1.0.)
6. dhclient shouldn't complain about missing dhclient-script??

Comment 1 Hans de Goede 2009-02-03 10:49:32 UTC
A patch fixing this has been committed to mkinitrd's git, so this will be fixed in the next rawhide build, closing.

Note You need to log in before you can comment on or make changes to this bug.