Okay so we have here first:
eth0 Link encap:Ethernet HWaddr 00:01:02:3B:DF:A3
inet6 addr: fe80::201:2ff:fe3b:dfa3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:285 errors:0 dropped:0 overruns:1 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:37909 (37.0 KiB) TX bytes:2430 (2.3 KiB)
Interrupt:10 Base address:0xb000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3619 errors:0 dropped:0 overruns:0 frame:0
TX packets:3619 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4425174 (4.2 MiB) TX bytes:4425174 (4.2 MiB)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 * 255.255.0.0 U 0 0 0 lo
This is the state of the ethernet interface before it's picked up an IP address. Then, once DHCP is complete:
eth0 Link encap:Ethernet HWaddr 00:01:02:3B:DF:A3
inet addr:192.168.0.34 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::201:2ff:fe3b:dfa3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:311 errors:0 dropped:0 overruns:1 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:42447 (41.4 KiB) TX bytes:5027 (4.9 KiB)
Interrupt:10 Base address:0xb000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3847 errors:0 dropped:0 overruns:0 frame:0
TX packets:3847 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4441198 (4.2 MiB) TX bytes:4441198 (4.2 MiB)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
So your Linux box has picked up the IP address 192.168.0.34 with a gateway of 192.168.0.1. Assuming there are no physical or authentication problems, you should be able to ping the gateway from the Linux box. Try it. Then try pinging something else that should normally work -
www.google.com, for example. Success would look something like this:
(#:~)- ping www.google.com
PING www.l.google.com (209.85.229.99) 56(84) bytes of data.
64 bytes from www.google.com (209.85.229.99): icmp_seq=1 ttl=245 time=36.0 ms
64 bytes from www.google.com (209.85.229.99): icmp_seq=2 ttl=245 time=36.4 ms
64 bytes from www.google.com (209.85.229.99): icmp_seq=3 ttl=245 time=35.1 ms
If your ping attempt returns an IP address for
www.google.com (as above), your network is complete. If no address is returned, then you have a DNS problem. Check out the contents of the /etc/resolv.conf file. They should be something like:
search local
nameserver 10.0.0.2
nameserver 212.23.6.100
nameserver 212.23.3.100
In this file the first line indicates that
computer.local is on my local domain so if I do "ping computer", the resolver will automatically change this to "ping computer.local". The other lines are my DNS servers, starting with my local router, followed by my ISP's.