Bug 425877
Summary: | network configurion with DHCP fails | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Praveen A <pravi.a> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | nyh, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-12-17 18:34:35 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Praveen A
2007-12-17 02:00:10 UTC
Set LINKDELAY if your network card takes a while to negotiate. See /usr/share/docs/initscripts-<version>/sysconfig.txt for details. Thanks. I have set LINKDELAY=20 in /etc/sysconfig/network-scripts/ifcfg-eth0 as you have suggested and it worked. It would be a good thing to set this if the DHCP server took longer during installation (not much useful for a laptop though). Also it would be better to have a reasonable value for this variable by default - especially since Windows and Debian did not have any problem with this network at all. I think it should wait longer by default since DHCP the network won't function without an IP and it is configyred for DHCP. And also messages like "link is not present, check cable" won't help. Can we check if the cable is present with mii-tool and if it is present give a more logical error message like, "your DHCP server is taking longer to respond". Once again thanks for the help. I had to run dhclient manually every time I boot up the machine. LINKDELAY has nothing to do with DHCP - it's that the actual link itself isn't coming up quickly (most likely due to switch configuration.) I think the original poster has made a good point. If we know that in some environments the 5 second default wait is too little, why not just increase the default? Like he said, on other systems like Debian or Ubuntu, this doesn't happen. If the network takes 20 seconds to come up than it's sad, but there is no point in giving up in 5 seconds... Given that on most modern systems, the network connection is vital, not some small we can only invest 5 seconds in trying. I also ran across this problem today in a corporate environment. Luckily I knew - and thought about - LINKDELAY. Most users will never be able to figure this out. When they see the message "Determining IP information for eth0... failed; no link present. Check cable?" I would think of two things (implicated in the message) - DHCP and the cable - and both are clearly irrelevant. I think this issue should be reopened. |