On 11/19/2014 1:11 PM, Robert Rea wrote:
Any ideas what to do with this. the first traceroute is to my most difficult site, the second to my ISP.
gandalf:/home/bob # traceroute nytimes.com traceroute to nytimes.com (170.149.168.130), 30 hops max, 40 byte packets using UDP 1 static.153.dscga.com (192.24.251.153) 0.356 ms 0.298 ms 0.298 ms 2 static.67f.dscga.com (209.49.173.67) 989.881 ms 1019.681 ms 1074.446 ms 3 static.65f.dscga.com (209.49.173.65) 1081.318 ms 1112.095 ms 1144.050
trimage
gandalf:/home/bob # traceroute dscga.com traceroute to dscga.com (209.116.1.3), 30 hops max, 40 byte packets using UDP 1 static.153.dscga.com (192.24.251.153) 0.368 ms 0.312 ms 0.366 ms 2 static.67f.dscga.com (209.49.173.67) 1847.238 ms 1862.114 ms 1889.100
All your problem is introduced on your first hop. Traceroute uses ping, and some ISPs block or delay ping. You can try with tcptraceroute dscga.com 80 to see if it is any better. Other than that, my first suggestion would be reboot your modem, because that is where all the delay kicks in. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org