Results 11 to 12 of 12
All right, finally some ifconfig output! And it's telling us by the lack of an "inet addr:" statement for eth0 that you're not getting a network address.
I'm going to ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 04-07-2006 #11
All right, finally some ifconfig output! And it's telling us by the lack of an "inet addr:" statement for eth0 that you're not getting a network address.
I'm going to assume that you have a DHCP server, either in the form of a router or your broadband modem if you're connecting directly to it. (You mentioned a hub in the first post; is it really just a hub, or is it a router?) In a terminal, issue the dhclient command:If that is successful, you'll get an address and should be up and running. Otherwise post the output here or Google for keywords that come up.Code:# dhclient eth0
Of course, if you're not using DHCP, then you'll have to set the address manually. That's easy to do, but if it still doesn't work after that, it's harder to troubleshoot.Stand up and be counted as a Linux user!
- 04-07-2006 #12Linux User
- Join Date
- Apr 2005
- Location
- Ohio
- Posts
- 326
Also the contents of etc/network/interfaces would be helpful. It could be a simple misconfiguration in your network settings..
cat /etc/network/interfaces
auto eth0 tells the system you want the interface to start automatically, the next line tels it to grab an address automatically through dhcpitg-debian:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcpfar...out


Reply With Quote
