Router issues with icmp?

[isf]

Can't appear to traceroute out of ntl network, tcptrace is fine. Can anybody else confirm?


ping -c 20 news.bbc.co.uk
PING newswww.bbc.net.uk (212.58.226.20) 56(84) bytes of data.
64 bytes from newslb11.thdo.bbc.co.uk (212.58.226.20): icmp_seq=3 ttl=54 time=34.5 ms
64 bytes from newslb11.thdo.bbc.co.uk (212.58.226.20): icmp_seq=4 ttl=54 time=18.7 ms
64 bytes from newslb11.thdo.bbc.co.uk (212.58.226.20): icmp_seq=5 ttl=54 time=19.4 ms
64 bytes from newslb11.thdo.bbc.co.uk (212.58.226.20): icmp_seq=6 ttl=54 time=22.2 ms
64 bytes from newslb11.thdo.bbc.co.uk (212.58.226.20): icmp_seq=7 ttl=54 time=19.4 ms
64 bytes from newslb11.thdo.bbc.co.uk (212.58.226.20): icmp_seq=8 ttl=54 time=18.6 ms
64 bytes from newslb11.thdo.bbc.co.uk (212.58.226.20): icmp_seq=9 ttl=54 time=38.0 ms
64 bytes from newslb11.thdo.bbc.co.uk (212.58.226.20): icmp_seq=10 ttl=54 time=18.1 ms

--- newswww.bbc.net.uk ping statistics ---
20 packets transmitted, 8 received, 60% packet loss, time 18999ms
rtt min/avg/max/mdev = 18.120/23.644/38.020/7.441 ms



sudo traceroute news.bbc.co.uk
traceroute to newswww.bbc.net.uk (212.58.226.33), 64 hops max, 52 byte packets
1 x.x.x.x (x.x.x.x) 1 ms 1 ms 1 ms
2 x.x.x.x (x.x.x.x) 9 ms 8 ms 8 ms
3 xxxx.inet.ntl.com (x.x.x.x) 9 ms 10 ms 8 ms
4 bagu-t3core-1b-ge-015-0.inet.ntl.com (195.182.175.45) 9 ms 11 ms 8 ms
5 lee-bb-b-so-130-0.inet.ntl.com (80.5.161.157) 11 ms 11 ms 8 ms
6 pop-bb-a-as1-0.inet.ntl.com (213.105.175.130) 15 ms 14 ms 16 ms
7 * * *
8 * * *
9 * * *
10 * * *



sudo tcptraceroute news.bbc.co.uk
Selected device eth0, address x.x.x.x, port 55750 for outgoing packets
Tracing the path to news.bbc.co.uk (212.58.226.8) on TCP port 80 (www), 30 hops max
1 x.x.x.x 1.015 ms 0.964 ms 1.057 ms
2 x.x.x.x 16.195 ms 54.837 ms 25.319 ms
3 xxxx.inet.ntl.com (x.x.x.x) 10.260 ms 11.089 ms 10.135 ms
4 bagu-t3core-1b-ge-017-0.inet.ntl.com (195.182.179.185) 24.876 ms 18.562 ms 9.628 ms
5 lee-bb-b-so-130-0.inet.ntl.com (80.5.161.157) 42.717 ms 22.250 ms 9.057 ms
6 pop-bb-a-as1-0.inet.ntl.com (213.105.175.130) 23.690 ms 15.702 ms 14.206 ms
7 pop-bb-b-ae0-0.inet.ntl.com (213.105.174.230) 15.523 ms 17.824 ms 17.392 ms
8 tele-ic-2-as0-0.inet.ntl.com (62.253.184.6) 17.787 ms 27.678 ms 13.758 ms
9 ntl-ge2-8.prt0.thdo.bbc.co.uk (212.58.239.217) 16.877 ms 41.377 ms 15.909 ms
10 212.58.238.129 37.555 ms 46.864 ms 17.757 ms
11 newslb14.thdo.bbc.co.uk (212.58.226.8) [open] 27.006 ms 25.185 ms 37.407 ms

[Graham M]

They look fine to me, the timeouts could be due to an overloaded router as ICMP packets normally get dropped if traffic volume is high

[Jon T]

works fine from here:

Tracing route to newswww.bbc.net.uk [212.58.226.20]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms efw-1209668945.localdomain [192.168.200
2 9 ms 6 ms 6 ms 10.225.80.1
3 8 ms 7 ms 7 ms nott-t2cam1-a-v107.inet.ntl.com [81.109

4 11 ms 7 ms 7 ms nott-t3core-1a-ge-013-0.inet.ntl.com [1
4.217]
5 10 ms 9 ms 12 ms lee-bb-a-as0-0.inet.ntl.com [213.105.17
6 13 ms 13 ms 14 ms pop-bb-b-as1-0.inet.ntl.com [62.253.185
7 16 ms 14 ms 14 ms tele-ic-2-as0-0.inet.ntl.com [62.253.18
8 18 ms 14 ms * ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.2
9 14 ms 15 ms 13 ms 212.58.238.153
10 16 ms 14 ms 14 ms newslb11.thdo.bbc.co.uk [212.58.226.20]

ping works on icmp echo requests, so that, and the fact my tracert works suggests that't not the problem.

ICMP does have lower prority than TCP/UDP traffic though, so the router could be dropping the ICMP packets if it's "a bit busy".

[r00t]

C:\Console>tracert www.bbc.net.uk

Tracing route to www.bbc.net.uk [212.58.253.71]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 8 ms 8 ms 10.4.xx.xx
3 7 ms 22 ms 7 ms 62.30.0.49
4 18 ms 18 ms 17 ms lee-bb-a-ge-320-0.inet.ntl.com [195.182.178.145]

5 52 ms 20 ms 17 ms pop-bb-b-as1-0.inet.ntl.com [62.253.185.238]
6 * * * Request timed out.
7 18 ms 17 ms 19 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
8 20 ms 15 ms 15 ms 212.58.238.129
9 20 ms 17 ms 17 ms te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
10 25 ms 17 ms 19 ms www2.cwwtf.bbc.co.uk [212.58.253.71]

Trace complete.

[Sirius]

Yep all fine here in Warrington
#


Tracing route to www.bbc.net.uk [212.58.251.215]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.0.1
2 10 ms 10 ms 14 ms 10.235.84.1
3 20 ms 6 ms 9 ms bagu-t2cam1-a-v121.inet.ntl.com [80.5.
4 26 ms 9 ms 13 ms bagu-t3core-1a-ge-017-0.inet.ntl.com
5 8 ms 10 ms 17 ms man-bb-a-so-310-0.inet.ntl.com [80.5.19.181]
6 27 ms 17 ms 14 ms gfd-bb-b-so-200-0.inet.ntl.com [62.252
7 16 ms 44 ms 16 ms redb-ic-1-as0-0.inet.ntl.com [62.253.1
8 20 ms 41 ms 29 ms 212.58.238.189
9 18 ms 17 ms 16 ms 212.58.238.133
10 17 ms 17 ms 19 ms 212.58.239.58
11 14 ms 16 ms 14 ms www8.telhc.bbc.co.uk [212.58.251.215]

[isf]

Thanks all.

The exact problem was severe SSH lag and timeouts when connecting to a specific server, I could SSH into to other machines fine. That's all working fine now, but I still can't traceroute anything outside the NTL network from home :wtf: