Red Hat Bugzilla – Bug 243586
dhclient bug prevents starting up networking
Last modified: 2007-11-30 17:12:07 EST
Description of problem:
On a Dell Dimension E520 with Intel Core2 Duo CPU and an integrated Intel
82562V 10/100 Network Connection with the e1000 driver on which I have
installed F7 x86_64 the boot process stops at:
'Bringing up interface eth0' and 'Determining IP information for eth0...'
shows a FAILURE and then continues booting. Result no networking.
Trying to '/sbin/ifup eth0' or '/sbin/ifdown eth0' freezes PC and I have to
pull the power plug.
A solution seems to be to 'NOT activate the device when computer starts'
then first delete the file "/var/lib/dhclient/dhclient-eth0.leases" and
only then to '/sbin/ifup eth0'.
Stangely I do not see this bug on a PC with a MSI K8N Neo2 Platinum
mainboard, nVidia nForce3 chipset, AMD64 3500+ CPU and Realtek RTL 8169
ethernet NIC where I have also installed F7 x86_64 so there might be
some hardware/driver connection.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install F7 x86_64 on a DEll Dimension E520 with same components
IP information collected correctly with result networking
I have a intel board with core2duo and f7-x86_64.
It shows the same behaviour as described above,
Strange is that when I press the reset switch of the computer before the failure
indication, the computer restarts and fully boots with the networking inplace
and doing what it is supposed to do.
My F8 box behaves identical.
Can you try if the following succeeds in getting networking going again ?:
system network stop
system network start
I can find no "system" command, not in /bin , /sbin , /usr/bin ,
Thanks for reply. I tried service network stop and service network start as you
suggested. This did not work.
In the mean time I installed kernel 3228 and the updates of june 15.
AND PRESTO, the effects I described earlier have gone. Reboot works through
networking without problems and the system now performs as expected.
Was it dhclient?, kernel or something else? Who knows.
My problem has SOLVED itself.
With the latest updates (kernel-2.6.21-1.3228?)
the problem seems to have been solved and
the network connection is established correctly
Reassigning to kernel component and marking as closed rawhide.