TerraNet dropping ICMP packets

samer

64 bytes from 72.14.234.104: icmp_seq=14 ttl=43 time=135.027 ms
64 bytes from 72.14.234.104: icmp_seq=15 ttl=43 time=135.787 ms
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
64 bytes from 72.14.234.104: icmp_seq=19 ttl=43 time=128.160 ms
64 bytes from 72.14.234.104: icmp_seq=20 ttl=43 time=129.395 ms
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
64 bytes from 72.14.234.104: icmp_seq=23 ttl=43 time=135.698 ms
64 bytes from 72.14.234.104: icmp_seq=24 ttl=43 time=138.741 ms
64 bytes from 72.14.234.104: icmp_seq=25 ttl=43 time=122.914 ms
Request timeout for icmp_seq 26
64 bytes from 72.14.234.104: icmp_seq=27 ttl=43 time=130.523 ms
Request timeout for icmp_seq 28
64 bytes from 72.14.234.104: icmp_seq=29 ttl=43 time=142.620 ms
Request timeout for icmp_seq 30
64 bytes from 72.14.234.104: icmp_seq=31 ttl=43 time=168.885 ms

This has been going on for a while… Any ideas on what's going on?

nuclearcat

Try this, to see on which hop it is happening
http://winmtr.sourceforge.net/

samer

I compiled MTR on OS X and ran it, here's the output:

http://cl.ly/1IHg

nuclearcat

It looks like their internal loss, probably call their support?
Maybe something on your link.

samer

It looks like their internal loss, probably call their support?

Should I even bother? The guy will probably not understand what the hell I'm talking about.

I ran a regular ping today, here's what I got:

$ ping google.com
PING google.com (72.14.234.104): 56 data bytes
36 bytes from 3.gi-0-1.core-6.terra.net.lb (212.98.136.61): Communication prohibited by filter
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 5400 2c09 0 0000 3b 01 5e7b 192.168.xx.xx 72.14.234.104

Thoughts on the bold part?

Kareem

Blocked hosts
Sometimes people don't want their hosts to be pinged and have configured their routers to block ping-packets. You might see such an output then:

1. [~] edwin@k7>ping www.mavetju.org
2. PING topaz.mdcc.cx (212.204.230.141): 56 data bytes
3. 36 bytes from gateway.widexs.net (212.204.214.161): Communication prohibited by filter
4. Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
5. 4 5 00 5400 d61f 0 0000 f1 01 ba99 203.173.128.219 212.204.230.141

The following information can be extracted from the output:

•Line 3:
◦The router filtering the traffic is gateway.widexs.net
◦The reason why it replied was Communication prohibited by filter. That means that the router was configured to block ping-packets towards that machine.

Source : http://www.mavetju.org/networking/basicnetworktroubleshooting.php