Pinging address - Packet Filtered

General networking problems and issues. Questions about cabling, switches, hubs etc. can go here.
Post Reply
jongi
Novice
Novice
Posts: 37
Joined: Tue Apr 24, 2007 8:49 am

Pinging address - Packet Filtered

Post by jongi » Tue Apr 29, 2008 11:18 am

I am getting the following ping result:

Code: Select all

[root:~#] ping o-lon-07.global-mix.net
PING o-lon-07.global-mix.net (91.193.244.214) 56(84) bytes of data.
From 78.41.155.149 icmp_seq=1 Packet filtered
From 78.41.155.149 icmp_seq=2 Packet filtered
From 78.41.155.149 icmp_seq=3 Packet filtered
From 78.41.155.149 icmp_seq=4 Packet filtered
From 78.41.155.149 icmp_seq=5 Packet filtered

--- o-lon-07.global-mix.net ping statistics ---
5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 58014ms
A traceroute to that address looks like it terminates. Or at least my results don't show up as they did for another user. The other user was o a different ISP that uses the same backbone as mine (the ISPs are both resellers).

Code: Select all

[root:~#] tracert o-lon-07.global-mix.net
traceroute to o-lon-07.global-mix.net (91.193.244.214), 30 hops max, 40 byte packets
 1  mygateway1.ar7 (192.168.1.1)  0.775 ms  1.018 ms  1.544 ms
 2  dsl-241-192-01.telkomadsl.co.za (41.241.192.1)  8.771 ms  10.827 ms  12.896 ms
 3  196.43.33.185 (196.43.33.185)  15.649 ms  17.187 ms *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * ge9-16.br02.ldn01.pccwbtn.net (63.218.13.13)  390.301 ms  391.414 ms
 9  datahop.ge10-9.br02.ldn01.pccwbtn.net (63.218.13.194)  403.511 ms  403.758 ms  403.908 ms
10  78.41.155.149 (78.41.155.149)  399.132 ms  399.928 ms  400.870 ms
11  78.41.155.149 (78.41.155.149)  402.588 ms !X  335.407 ms !X *
It is the first time I have seen a traceroute end with !X *.
mstombs
RouterTech Team
RouterTech Team
Posts: 3753
Joined: Wed Jan 10, 2007 11:54 pm

Post by mstombs » Tue Apr 29, 2008 12:16 pm

I'm a bit closer to that address than you!

Code: Select all

>tracert o-lon-07.global-mix.net

Tracing route to o-lon-07.global-mix.net [91.193.244.214]
over a maximum of 30 hops:
...
  8     4 ms     3 ms     3 ms  linx224.global-mix.net [195.66.224.217]
  9  linx224.global-mix.net [195.66.224.217]  reports: Destination net unreachab
le.

Trace complete.

>ping o-lon-07.global-mix.net

Pinging o-lon-07.global-mix.net [91.193.244.214] with 32 bytes of data:

Reply from 195.66.224.217: Destination net unreachable.
Reply from 195.66.224.217: Destination net unreachable.
Reply from 195.66.224.217: Destination net unreachable.
Reply from 195.66.224.217: Destination net unreachable.

Ping statistics for 91.193.244.214:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Its just configured to not respond to ping I guess!
cb
Novice
Novice
Posts: 30
Joined: Sat Apr 12, 2008 9:40 pm
Location: Newcastle-under-Lyme

Post by cb » Fri May 02, 2008 7:48 pm

It does look like it's configured to drop pings.

Code: Select all

$ ping -c 5 o-lon-07.global-mix.net 
PING o-lon-07.global-mix.net (91.193.244.214) 56(84) bytes of data.
From 91.193.244.137 icmp_seq=1 Packet filtered
From 91.193.244.137 icmp_seq=2 Packet filtered
From 91.193.244.137 icmp_seq=3 Packet filtered
From 91.193.244.137 icmp_seq=4 Packet filtered
From 91.193.244.137 icmp_seq=5 Packet filtered
But if I try traceroute with the -T option, I do get a trace. This uses TCP SYN packets as the probes.

Code: Select all

$ sudo tracert -T o-lon-07.global-mix.net
traceroute to o-lon-07.global-mix.net (91.193.244.214), 30 hops max, 40 byte packets
 1  sar-600ew.ar7 (192.168.1.1)  4.579 ms  4.944 ms  5.514 ms
 2  fir.dsl.enta.net (87.127.229.35)  49.803 ms  52.512 ms  54.578 ms
 3  vlan4003.telehouse-east2.dsl.enta.net (87.127.229.33)  55.782 ms  57.116 ms  59.052 ms
 4  gi1-8.telehouse-east2.core.enta.net (62.249.192.125)  60.742 ms  62.342 ms  64.697 ms
 5  87-127-231-18.no-dns-yet.enta.net (87.127.231.18)  259.847 ms  260.292 ms  260.986 ms
 6  tengu-wolverine.c4l.co.uk (84.45.90.157)  71.978 ms  59.530 ms  60.884 ms
 7  84.45.24.178 (84.45.24.178)  63.175 ms  47.806 ms  49.465 ms
 8  91.193.244.137 (91.193.244.137)  230.018 ms * *
 9  o-lon-07.global-mix.net (91.193.244.214)  47.852 ms * *
I guess the gateway in front (91.193.244.137) of the destination is blocking the ping. Reading the man pages, turns out "!X" means "communication administratively prohibited", so I've learnt something!
User avatar
eMuNiX
Ex RouterTech Team
Ex RouterTech Team
Posts: 901
Joined: Sat Jan 28, 2006 9:02 am
Contact:

Post by eMuNiX » Sat May 03, 2008 12:39 pm

A trace from my linux box gives:-

emunix@emunix-desktop:~$ sudo traceroute 91.193.244.217
traceroute to 91.193.244.217 (91.193.244.217), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1 ms 1 ms 1 ms
2 cr1.ndhas.uk.easynet.net (87.87.252.103) 27 ms 22 ms 23 ms
3 ip-87-87-154-65.easynet.co.uk (87.87.154.65) 19 ms 19 ms 19 ms
4 be2.er10.thlon.ov.easynet.net (195.66.224.43) 29 ms 29 ms 28 ms
5 linx224.global-mix.net (195.66.224.217) 50 ms * 210 ms
Image
Post Reply