I can't get a web page to display. My router pings ok (192.168.1.100) but I can't ping google. Here are a few diagnostic tests I ran.
Here is my output:
[root@localhost ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 1C:6F:65:30:F3:34
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:33 Base address:0x6000
eth1 Link encap:Ethernet HWaddr 00:50:B6:05:FB:34
inet addr:192.168.1.100 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::250:b6ff:fe05:fb34/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3316 (3.2 KiB) TX bytes:6053 (5.9 KiB)
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:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:880 (880.0 b) TX bytes:880 (880.0 b)
[root@localhost ~]# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 209.18.47.61
nameserver 209.18.47.62
search cinci.rr.com
It would appear you are pinging your
localhost, not your router. The router would have to have a
different IP than your
eth1.
On my machine:[root@fatman ~]# ifconfigeth0 Link encap:Ethernet HWaddr 00:1F:D0:BD:54:7D
inet addr:
192.168.1.99 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21f:d0ff:febd:547d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:35737398 errors:0 dropped:0 overruns:0 frame:0
TX packets:38755140 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1534498429 (1.4 GiB) TX bytes:612699835 (584.3 MiB)
Interrupt:42 Base address:0x4000
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:51542 errors:0 dropped:0 overruns:0 frame:0
TX packets:51542 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3033071 (2.8 MiB) TX bytes:3033071 (2.8 MiB)
To ping my router:[root@fatman ~]# ping -c3 192.168.1.1PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=150 time=0.240 ms
64 bytes from 192.168.1.1: icmp_req=2 ttl=150 time=0.242 ms
64 bytes from 192.168.1.1: icmp_req=3 ttl=150 time=222 ms
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.240/74.186/222.077/104.574 ms
To ping the modem:[root@fatman ~]# ping -c3 192.168.100.1PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_req=1 ttl=64 time=2.27 ms
64 bytes from 192.168.100.1: icmp_req=2 ttl=64 time=1.54 ms
64 bytes from 192.168.100.1: icmp_req=3 ttl=64 time=1.53 ms
--- 192.168.100.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.537/1.787/2.276/0.345 ms
To ping the DNS server:[root@fatman ~]# ping -c3 4.2.2.2PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
64 bytes from 4.2.2.2: icmp_req=1 ttl=54 time=256 ms
64 bytes from 4.2.2.2: icmp_req=2 ttl=54 time=15.4 ms
64 bytes from 4.2.2.2: icmp_req=3 ttl=54 time=15.5 ms
--- 4.2.2.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 15.419/95.876/256.645/113.680 ms
To ping Google:[root@fatman ~]# ping -c3 google.comPING google.com (74.125.225.16) 56(84) bytes of data.
64 bytes from 74.125.225.16: icmp_req=1 ttl=55 time=20.5 ms
64 bytes from 74.125.225.16: icmp_req=2 ttl=55 time=21.9 ms
64 bytes from 74.125.225.16: icmp_req=3 ttl=55 time=17.2 ms
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 6091ms
rtt min/avg/max/mdev = 17.200/19.883/21.905/1.983 ms
By pinging in this order any break in the Internet connection can be isolated as to
where the breakdown
actually occurs. If I can reach the router the first link in the chain, between my machine and the router, is good. If I can reach the modem, the link between it and the router is good. If I can reach the DNS server, the modem is working properly, and lastly if the DNS server can translate
google.com to a
proper IP address, it too is working properly and my connection to the rest of the Internet is complete.
