Re: network issues
On 09/26/08 11:08, Paul Cartwright wrote:
Running Debian Lenny. I am not sure my network is functioning
correctly, OR I have a problem with my ISP or DNS...
what does this tell you:
traceroute microsoft.com
Try mtr. It gives more detail, and, IMO, more useful detail.
traceroute to microsoft.com (207.46.197.32), 30 hops max, 40 byte packets
1 192.168.10.1 (192.168.10.1) 1.270 ms 1.553 ms 1.819 ms
2 208.65.88.129 (208.65.88.129) 13.575 ms 16.686 ms *
3 * * *
4 * * *
5 * * *
6 * * te3-4.ccr02.dca01.atlas.cogentco.com (154.54.7.210) 28.492 ms
7 te2-2.ccr02.dca01.atlas.cogentco.com (154.54.7.141) 30.814 ms
vl3498.mpd01.dca02.atlas.cogentco.com (154.54.7.6) 25.882 ms
te2-2.ccr02.dca01.atlas.cogentco.com (154.54.7.141) 28.586 ms
8 vl3493.mpd01.dca02.atlas.cogentco.com (154.54.7.230) 32.446 ms
te1-2.ccr02.iad01.atlas.cogentco.com (154.54.7.158) 35.574 ms 38.992 ms
9 * * *
10 * * *
11 * * *
12 * ge-7-1-0-0.blu-64c-1b.ntwk.msn.net (207.46.33.10) 39.432 ms *
13 ge-7-1-0-0.cpk-64c-1a.ntwk.msn.net (207.46.35.37) 99.083 ms * *
14 * * ge-7-1-0-0.cpk-64c-1a.ntwk.msn.net (207.46.35.37) 95.032 ms
15 ten3-4.cpk-76c-1b.ntwk.msn.net (207.46.34.118) 95.073 ms 94.551
ms 10.22.0.30 (10.22.0.30) 95.334 ms
16 * * 10.22.0.30 (10.22.0.30) 99.252 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
my ISP is atnex.net, here is a traceroute from me to them:
traceroute atnex.net
traceroute to atnex.net (208.65.89.2), 30 hops max, 40 byte packets
1 192.168.10.1 (192.168.10.1) 1.267 ms 1.589 ms 1.863 ms
2 208.65.88.129 (208.65.88.129) 13.124 ms 16.238 ms *
3 * * *
4 * * *
5 * * *
6 * 208.65.88.21 (208.65.88.21) 11.353 ms !X *
cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.10.1
nameserver 208.67.222.222
nameserver 208.67.220.220
ping 208.67.222.222
PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data.
64 bytes from 208.67.222.222: icmp_seq=1 ttl=54 time=1610 ms
64 bytes from 208.67.222.222: icmp_seq=2 ttl=54 time=1546 ms
64 bytes from 208.67.222.222: icmp_seq=3 ttl=54 time=1605 ms
64 bytes from 208.67.222.222: icmp_seq=4 ttl=54 time=1545 ms
Your packets are getting beyond your router, so it can't be your fault.
--
Ron Johnson, Jr.
Jefferson LA USA
"Do not bite at the bait of pleasure till you know there is no
hook beneath it." -- Thomas Jefferson
Reply to: