Networking Forums

Networking Forums > Computer Networking > Linux Networking > RedHat Linux Enterprise WS network lan dhcp script problem.

Reply
Thread Tools Display Modes

RedHat Linux Enterprise WS network lan dhcp script problem.

 
 
CaptWiggum@gmail.com
Guest
Posts: n/a

 
      04-21-2005, 03:17 PM
SUMMARY:

RedHat Linux Enterprise WS network lan dhcp startup
scripts problem. The bootup rc script reports:
"failed; no link present. Check cable?"

But if I plug the same cable into a mac or windows pc,
then it works fine. I know the cable and network are good.
What's more, this behavior is the same on two brand new
dell / redhat systems. So I don't think its a bad card.

Solution:

First, many people told me that dhclient did not work for
them, so I downloaded the 'pump' RPM to replace dhclient,
and edited the the ifup script to try pump first, before
dhclient. Then "ifup eth0" would work from the command
line after boot, but still would not work during boot.

I think there is a bug in one of the rc scripts.
Detail below, but the fix was simply to edit the file:
/etc/sysconfig/network-scripts/ifup
and comment out these lines, beginning around line 240:

# echo
# echo -n $"Determining IP information for ${DEVICE}..."
# if check_link_down ${DEVICE}; then
# echo $" failed; no link present. Check cable?"
# ip link set dev ${DEVICE} down >/dev/null 2>&1
# exit 1
# fi

After commenting out, I reboot, and all works fine.

DETAIL:

When booting, the network rc script calls the ifup script.
It fails with the message above. But, after it boots, if
I go to a terminal, su to root, and do a "ifup eth0", then
it works fine. But I did not want to have to do this every
time I booted. I wanted to fix the rc scripts.
So I investigated this...

On boot, /etc/rc.d/* will call the script with param:
"init.d/network start"
This will call the script
"/etc/sysconfig/network-scripts/ifup eth0"
That sources the support file
"/etc/sysconfig/network-scripts/network-functions"
which has a function in it called check_link_down

Now, ifup calls check_link_down, which loops for 5
seconds, and checks every 1/2 second for good values.
Good values are a "Link detected: yes" from ethtool,
and "link ok" from mii-tool. Both of these tools just
check the very low level status of the interface.

I looks like check_link_down fails if the link is UP
instead of down. That seems backwards to me. Maybe
it previously set it down, and it is waiting for it to go
down. I don't know. I just know this Dell / RedHat combo
did not work with it. The above simple edit fixes it.

Hope this helps someone!

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Redhat Linux 8 and Redhat Enterprise Linux 4 printer not configure Niraj Linux Networking 0 12-06-2006 04:51 AM
1. Redhat linux 7.2 issue 2. Redhat enterprise linux issue Moo Linux Networking 0 08-26-2004 10:02 AM
Red Hot Linux v9.0 [2 DVDs]. Red Hot Linux v9.0 [3 CDs]. Redhat Enterprise Linux ES v3.0 REPACK [4 CDs]. Mandrake Linux 9.2 [3 CDs] -new ! TEL Linux Networking 0 12-01-2003 12:06 PM
Red Hot Linux v9.0 [2 DVDs]. Red Hot Linux v9.0 [3 CDs]. Redhat Enterprise Linux ES v3.0 REPACK [4 CDs]. Mandrake Linux 9.2 [3 CDs] - new ! TEL Linux Networking 0 11-29-2003 11:27 AM
Browsing a Windows Network from RedHat Enterprise WS Jim Charier Linux Networking 0 11-13-2003 05:55 PM



1 2 3 4 5 6 7 8 9 10 11