LebGeeks

recon1025

Member

Puzzling response by tracert and ping

Hi, this is another posting relating to the broadband that i obtained today.
When I try trace routing any ip/FQDN i recieve the following response:

C:>tracert www.lebgeeks.com

Tracing route to lebgeeks.com [209.120.238.90]
over a maximum of 30 hops:

  1    63 ms    29 ms    37 ms  172.16.206.1
  2     *     192.168.108.30  reports: Destination net unreachable.

Trace complete.

Now that's really puzzling because i can successfuly connect to this site or any other site for that matter but for some reason ping and tracert report that problem. Could it be because the isp is filtering ICMP at their server end? Or is this a more severe problem than just a firewall blocking icmp packets? Your help/opinion is greatly appreciated.
<br>
P.S: Notice the round trip time it takes for the first gateway! Pretty lame QoS.

nuclearcat

Member

Re: Puzzling response by tracert and ping

I heard they have sessions limit?

Sadus

Member

Re: Puzzling response by tracert and ping

sure that most of local ISPs filter their ICMP, i really don't understand why, if they're afraid of DoS then, alot of solution are there, anyhow. when you connect to lebgeeks from your browser, its done via TCP port 80, so this has really nothing to do with icmp.

it also doesn't mean that your ISP is bad, my ISP can tracert untill it reaches europe, then the routers there drop my trace request.

nuclearcat

Member

Re: Puzzling response by tracert and ping

They are affraid someone will see what backbone links they use :)

rolf

Member

Re: Puzzling response by tracert and ping

P.S: Notice the round trip time it takes for the first gateway! Pretty lame QoS.

Is that a terranet connection? If that's a terranet connection, wait till it reaches the terranet satellite backbone, the latency will jump to 600ms!
Talking about a lame QoS.

rolf

Member

Re: Puzzling response by tracert and ping

They are affraid someone will see what backbone links they use :)

Oh not a big deal

for terranet for example, we do a traceroute from the USA on this site
http://master2.dca1.superb.net/cgi-bin/ … rra.net.lb
Note how bit di3 el tase as soon as the packet arrive in the terranet network. These people seem to have a problem with ICMP :) .

You can also open this page and select any traceroute in the "Tools" section on the left menu:
http://nsssc.superb.net/information/corenet-info.php

then a traceroute from my linux box on my terranet "broadband (yeah sure)" connection. Note that the linux traceroute is different than the windows traceroute in that it does not give up when it receives a "network not reachable error"

[root@hello root]# traceroute www.fbi.gov
traceroute: Warning: www.fbi.gov has multiple addresses; using 66.178.61.169
traceroute to a33.g.akamai.net (66.178.61.169), 30 hops max, 38 byte packets
1  172.16.206.1 (172.16.206.1)  37.365 ms  36.268 ms  35.963 ms
2  192.168.108.30 (192.168.108.30)  32.956 ms  42.324 ms  37.525 ms
3  * * *
4  core-2.terra.net.lb (212.98.136.55)  39.202 ms  72.948 ms  51.700 ms
5  se-2-5.core-5.terra.net.lb (212.98.146.162)  48.743 ms  39.260 ms  32.936 ms
6  66-178-4-9.reverse.newskies.net (66.178.4.9)  703.535 ms  669.294 ms  611.162 ms
7  rtr-cor01-vlan2.man.newskies.net (66.178.0.81)  620.255 ms  622.671 ms  628.449 ms
8  rtr-col01-fa0-0.man.newskies.net (66.178.61.10)  626.942 ms  647.501 ms  621.718 ms
9  66-178-61-169.reverse.newskies.net (66.178.61.169)  624.646 ms  644.813 ms  623.175 ms

It's obvious, they have a newskies satellite backbone (hence the lag)
(company site: http://www.newskies.com/ )