Bringing up interface eth0 determining IP information fails
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Bringing up interface eth0 determining IP information fails
CentOS 4.7 a minimal installation with no GUI
Ethernet Controller RTL-8029
Running /sbin/lspci shows the Ethernet card....
ifcfg-eth0 shows BOOTPROTO=dhcp
NIC is connected to a LINKSYS WRT54G running DHCP. There are plenty of available IP assignments. All other PC that I have connected to the LINKSYS work fine. The CAT 5 cable is fine.
From the sounds of it, it *should* work. A couple of observations/suggestions:
1. It sounds like you're knowledgeable, and that you're doing everything right.
2. You imply you've got an Ethernet adapter (not wifi), and you're plugging it directly into your WRT54G router.
Q: is this correct?
3. If so, please double-check your /sbin/ifconfig output, and DISABLE all interfaces besides your eth0. Don't mess with multiple interfaces until we get *one* interface working.
4. The problem clearly appears to be DHCP.
Q: Have you considered simply assigning a static address (if only for debugging purposes)?
I have quite a few years of technical experience so Im not exactly a newbie ;-)
Yes, I have a Ethernet card with a CAT 5 cable connected to the router.
eth0 is the only interface at this point aside from local loopback.
Static assignment ? I still want to understand why assignment is not happening dynamically. If need be, we can go that route.
Quote:
Originally Posted by paulsm4
Hi -
From the sounds of it, it *should* work. A couple of observations/suggestions:
1. It sounds like you're knowledgeable, and that you're doing everything right.
2. You imply you've got an Ethernet adapter (not wifi), and you're plugging it directly into your WRT54G router.
Q: is this correct?
3. If so, please double-check your /sbin/ifconfig output, and DISABLE all interfaces besides your eth0. Don't mess with multiple interfaces until we get *one* interface working.
4. The problem clearly appears to be DHCP.
Q: Have you considered simply assigning a static address (if only for debugging purposes)?
Last edited by chickonlinux; 10-16-2010 at 09:26 PM.
Reason: typo
Well, you can always try a network trace to see who's dropping the ball. You can use tcpdump (cmd-line) on Centos, or Wireshark on any of the other PCs on your LAN.
There might be some kind of conflict between Netmanager and your low-level configuration files (such as /etc/sysconfig/network-scripts/ifcfg-eth0, which I believe you cited in your original post). Who knows - Centos might also have some firewall setting that's blocking DHCP. But I think I'm stretching...
If it's no hassle, try seeing if a static address works.
And if so, double-check the settings in your /etc/sysconfig/network-scripts and/or go back to DHCP and try taking a network trace.
Q: If so, what was the problem?
If not, perhaps maybe I could install CentOS 4.7 on a VM and try reproducing it? (I'm currently running CentOS 5.5 on a VPS, but that's not really applicable to your scenario).
Nope, I upgraded to CentOS 4.8 because my application allowed that. I acutally ordered a new ethernet card that is stated to be compatible with Linux. My current card uses a RTL8029 chipset which is a commonly used chipset though.
Quote:
Originally Posted by paulsm4
Hi, Stephanie -
Q: Did you get it working?
Q: If so, what was the problem?
If not, perhaps maybe I could install CentOS 4.7 on a VM and try reproducing it? (I'm currently running CentOS 5.5 on a VPS, but that's not really applicable to your scenario).
/sbin/dhclient eth0
Internet Systems Consortium DHCP Client V3.0.5-RedHat
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
/sbin/dhclient-script: configuration for eth0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 78: eth0: No such file or directory
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
eth0: unknown interface: No such device
Failed to get interface index: No such device
3. ethtool eth0 ("ethtool" is generally preferred over "mii-tool"):
Code:
/usr/sbin/ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: yes
4. less /var/log/messages
<= Cut/paste any messages related to the failed DHCP request(s)
... and, most importantly ...
5. dhcpcd -r
Code:
/sbin/dhcpcd -r
**** /sbin/dhcpcd: already running
**** /sbin/dhcpcd: if not then delete /var/run//dhcpcd-eth0.pid file
Getting information off the machine onto this machine is a bit of an issue.
I can summarize the results this way:
ifconfig eth0: shows no assigned inet addr, states UP BROADCAST RUNNING MULTICAST, 18 RX packet errors & 7 TX packet errors
dhclient eth0: shows several DHCPDISCOVER attempt messages and finally NO DHCP OFFERS received
ethtool eth0: showed results similar to your "code" results. Actually, the RTL8029 NIC showed "NO DATA AVAILABLE" after running ethtool. My new DLINK NIC showed a whole table of results.
less /var/log/messages: showed ifup failed. Bringing up interfae eth0 failed. Saw a number of NETDEV WATCHDOG eth0 transmit timed out messages
dhcpcd does not exist in sbin...this is the client daemon ? If I type dhclient again it tells me its already running.
Quote:
Originally Posted by paulsm4
OK, then please cut/paste the exact output of the following:
/sbin/dhclient eth0
Internet Systems Consortium DHCP Client V3.0.5-RedHat
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
/sbin/dhclient-script: configuration for eth0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 78: eth0: No such file or directory
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
eth0: unknown interface: No such device
Failed to get interface index: No such device
3. ethtool eth0 ("ethtool" is generally preferred over "mii-tool"):
Code:
/usr/sbin/ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: yes
4. less /var/log/messages
<= Cut/paste any messages related to the failed DHCP request(s)
... and, most importantly ...
5. dhcpcd -r
Code:
/sbin/dhcpcd -r
**** /sbin/dhcpcd: already running
**** /sbin/dhcpcd: if not then delete /var/run//dhcpcd-eth0.pid file
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.