cancel
Showing results for 
Search instead for 
Did you mean: 

Outbound *nix traceroute?

Community Gaffer
Community Gaffer
Posts: 13,423
Thanks: 1,184
Fixes: 92
Registered: 04-04-2007

Outbound *nix traceroute?

Hi all,
Anybody got a Unix box on their Plusnet line and able to run an outbound traceroute to somewhere outside of the Plusnet network for me? I'm curious to see how far it gets.

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵

10 REPLIES
Community Veteran
Posts: 5,457
Thanks: 1,434
Fixes: 34
Registered: 16-10-2014

Re: Outbound *nix traceroute?

Is this any use?

iMac:~ Mook$ traceroute postgresql.org
traceroute to postgresql.org (217.196.149.50), 64 hops max, 52 byte packets
1  router (192.168.0.1)  3.584 ms  3.392 ms  5.266 ms
2  lo0-central10.pcl-ag02.plus.net (195.166.128.183)  55.294 ms  43.929 ms  39.894 ms
3  link-b-central10.pcl-gw02.plus.net (212.159.2.166)  40.089 ms  40.855 ms  40.825 ms
4  xe-10-1-0.pcl-cr02.plus.net (212.159.0.198)  39.883 ms  43.923 ms  39.996 ms
5  ae1.ptw-cr02.plus.net (195.166.129.2)  40.749 ms  40.209 ms  42.672 ms
6  lonap1.thn.lon.neotelecoms.com (5.57.80.210)  40.391 ms  39.511 ms  41.227 ms
7  ae4.tcr1.rb.par.core.as8218.eu (83.167.63.231)  54.730 ms  48.209 ms  48.453 ms
8  ae9.tcr1.vix.vie.core.as8218.eu (83.167.56.155)  64.943 ms  65.465 ms  65.240 ms
9  xe0-1-1.r06.uni.vie.at.nextlayer.net (212.69.191.150)  64.796 ms  66.376 ms  65.116 ms
10  ae11.r01.prf.vie.at.nextlayer.net (92.60.3.249)  65.988 ms
    ae10.r01.prf.vie.at.nextlayer.net (92.60.2.249)  65.755 ms
    ae11.r01.prf.vie.at.nextlayer.net (92.60.3.249)  67.649 ms
11  xe-0-0-31.r01.tnz.sbg.at.nextlayer.net (92.60.3.6)  69.725 ms  69.800 ms  69.796 ms
12  213.208.148.110 (213.208.148.110)  70.002 ms  69.589 ms  69.917 ms
13  lo10-c4.infra.conova.net (217.196.145.171)  69.534 ms  71.566 ms  71.110 ms
14  217.196.145.169 (217.196.145.169)  71.597 ms  70.307 ms  70.854 ms
15  zalkon.postgresql.org (217.196.149.50)  69.693 ms  69.849 ms  70.747 ms

Community Gaffer
Community Gaffer
Posts: 13,423
Thanks: 1,184
Fixes: 92
Registered: 04-04-2007

Re: Outbound *nix traceroute?

Yes, thanks.
I get similar results to that domain.
Reason I asked is that I've been scratching my head as to why I've been unable to run traceroutes to certain addresses. Admittedly I only tried a couple of hostnames but they've been timing out at the edge of our network. ICMP traces from a Windows box are fine. Now that I've realised it's not affecting all addresses, it looks like it might just be stuff that we have peering/caching arrangements with:
~$ traceroute bbc.co.uk
traceroute to bbc.co.uk (212.58.244.20), 30 hops max, 60 byte packets
1  192.168.1.254 (192.168.1.254)  7.758 ms  7.433 ms  24.204 ms
2  lo0.11.central11.ptw-bng01.plus.net (195.166.128.171)  23.814 ms  23.558 ms  23.325 ms
3  irb.11.PTW-CR02.plus.net (84.93.249.18)  23.094 ms  22.845 ms irb.11.PTW-CR01.plus.net (84.93.249.17)  22.562 ms
4  * * ae2.ptw-cr01.plus.net (195.166.129.4)  21.809 ms
5  * * *
6  * * *
7  * * *
8  * * *

~$ traceroute google.com
traceroute to google.com (212.56.71.89), 30 hops max, 60 byte packets
1  192.168.1.254 (192.168.1.254)  5.231 ms  4.915 ms  12.184 ms
2  lo0.11.central11.ptw-bng01.plus.net (195.166.128.171)  30.918 ms  30.636 ms  30.398 ms
3  irb.11.PTW-CR02.plus.net (84.93.249.18)  30.154 ms irb.11.PTW-CR01.plus.net (84.93.249.17)  29.699 ms  29.791 ms
4  ae1.pcl-cr01.plus.net (195.166.129.1)  29.186 ms ae2.ptw-cr02.plus.net (195.166.129.5)  29.322 ms  29.094 ms
5  * ae2.pcl-cr02.plus.net (195.166.129.7)  28.627 ms *
6  * * *
7  * * *
8  * * *
9  * * *

I could be wrong, but I'm sure it's not always been like this?

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵

Community Veteran
Posts: 5,457
Thanks: 1,434
Fixes: 34
Registered: 16-10-2014

Re: Outbound *nix traceroute?

Well doing the same as yourself:

iMac:~ Mook$ traceroute bbc.co.uk
traceroute: Warning: bbc.co.uk has multiple addresses; using 212.58.244.20
traceroute to bbc.co.uk (212.58.244.20), 64 hops max, 52 byte packets
1  router (192.168.0.1)  3.555 ms  5.557 ms  5.164 ms
2  lo0-central10.ptw-ag04.plus.net (195.166.128.194)  42.128 ms  40.053 ms  40.352 ms
3  link-a-central10.ptw-gw01.plus.net (212.159.2.156)  40.221 ms  39.984 ms  39.602 ms
4  xe-7-2-0.ptw-cr01.plus.net (212.159.0.252)  40.152 ms  44.132 ms  39.391 ms
5  * * *
6  * * *
7  * * *
8  * * *
9  * * *
10  * * *
11  * * *
12  * *^C


iMac:~ Mook$ traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 212.56.71.54
traceroute to google.com (212.56.71.54), 64 hops max, 52 byte packets
1  router (192.168.0.1)  3.599 ms  3.478 ms  4.604 ms
2  lo0-central10.pcl-ag02.plus.net (195.166.128.183)  40.915 ms  41.830 ms  39.912 ms
3  link-a-central10.pcl-gw01.plus.net (212.159.2.164)  40.412 ms  41.579 ms  40.830 ms
4  xe-10-1-0.pcl-cr01.plus.net (212.159.0.196)  120.928 ms  40.150 ms  40.321 ms
5  * * *
6  * * *
7  * * *
8  * * *
9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * *^C
pwatson
Rising Star
Posts: 2,468
Thanks: 8
Fixes: 1
Registered: 26-11-2012

Re: Outbound *nix traceroute?

If it helps, I get the same issue using my Entanet connection - A traceroute from a Raspberry Pi stops as the traffic leaves Telehouse whereas a Windows tracert shows the next hop in Linx and carries on.  Forcing the Pi to use ICMP (-I switch) rather than UDP works as per Windows.
Community Gaffer
Community Gaffer
Posts: 13,423
Thanks: 1,184
Fixes: 92
Registered: 04-04-2007

Re: Outbound *nix traceroute?

Quote from: pwatson
If it helps, I get the same issue using my Entanet connection - A traceroute from a Raspberry Pi stops as the traffic leaves Telehouse...

Fair enough, perhaps it's always been like this then (although it's only certain destinations it's happening with). ICMP does complete, albeit with non-responsive hops in between.
~$ sudo traceroute -I google.com
traceroute to google.com (212.56.71.218), 30 hops max, 60 byte packets
1  192.168.1.254 (192.168.1.254)  8.096 ms  7.919 ms *
2  * * *
3  * * *
4  * * *
5  * * *
6  * ggc01.plus.net (212.56.71.218)  29.072 ms  28.430 ms

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵

pwatson
Rising Star
Posts: 2,468
Thanks: 8
Fixes: 1
Registered: 26-11-2012

Re: Outbound *nix traceroute?

ICMP
traceroute 212.58.244.20 -I
traceroute to 212.58.244.20 (212.58.244.20), 30 hops max, 60 byte packets
1  billion.home.gateway (192.168.5.254)  0.956 ms  0.994 ms  0.806 ms
2  lns12.inx.dsl.enta.net (188.39.1.6)  8.473 ms  8.854 ms  8.323 ms
3  te3-3.inx.dist.dsl.enta.net (188.39.1.5)  8.528 ms  8.298 ms  8.123 ms
4  te2-2.interxion.dsl.enta.net (78.33.141.89)  8.279 ms  8.108 ms  7.937 ms
5  te2-3.interxion.core.enta.net (87.127.236.209)  8.077 ms  8.310 ms  8.465 ms
6  te0-1-1-1.interxion3.core.enta.net (188.39.127.164)  8.707 ms  8.645 ms  8.434 ms
7  te0-0-0-3.telehouse-north.core.enta.net (188.39.127.171)  9.261 ms  9.627 ms  8.802 ms
8  bbc-linx.pr01.rbsov.bbc.co.uk (195.66.236.103)  8.869 ms  8.551 ms  8.306 ms
9  * * *
10  * * *
11  ae0.er01.telhc.bbc.co.uk (132.185.254.109)  8.882 ms  9.252 ms  8.824 ms
12  132.185.255.149 (132.185.255.149)  9.466 ms  8.971 ms  9.086 ms
13  fmt-vip71.telhc.bbc.co.uk (212.58.244.20)  8.511 ms  8.327 ms  9.896 ms

UDP
traceroute 212.58.244.20
traceroute to 212.58.244.20 (212.58.244.20), 30 hops max, 60 byte packets
1  billion.home.gateway (192.168.5.254)  1.368 ms  1.131 ms  0.942 ms
2  lns12.inx.dsl.enta.net (188.39.1.6)  8.287 ms  7.696 ms  8.096 ms
3  te3-3.inx.dist.dsl.enta.net (188.39.1.5)  7.751 ms  7.763 ms  7.834 ms
4  te2-2.interxion.dsl.enta.net (78.33.141.89)  7.871 ms  8.355 ms  8.380 ms
5  te2-3.interxion.core.enta.net (87.127.236.209)  8.354 ms  8.299 ms  8.352 ms
6  te0-1-1-1.interxion3.core.enta.net (188.39.127.164)  8.877 ms  8.923 ms  8.883 ms
7  te0-0-0-3.telehouse-north.core.enta.net (188.39.127.171)  8.940 ms  10.906 ms  10.985 ms
8  * * *
9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *

Community Veteran
Posts: 1,136
Thanks: 2
Registered: 30-07-2007

Re: Outbound *nix traceroute?

One of your core routers is probably blocking the UDP pings for you.
Try changing gateway?  Grin Grin
adw@nofate:~$ traceroute www.google.com
traceroute to www.google.com (64.233.184.104), 30 hops max, 60 byte packets
1  thundertank.avatastic.co.uk (10.0.1.254)  0.584 ms  0.790 ms  0.843 ms
2  195.166.130.210 (195.166.130.210)  13.173 ms  13.617 ms  13.623 ms
3  link2-central10.pcl-gw02.plus.net (84.93.249.162)  14.579 ms  14.593 ms  14.594 ms
4  ae1.ptw-cr01.plus.net (195.166.129.0)  14.571 ms ae1.ptw-cr02.plus.net (195.166.129.2)  14.788 ms ae2.pcl-cr01.plus.net (195.166.129.6)  15.005 ms
5  72.14.223.32 (72.14.223.32)  15.591 ms  15.631 ms  15.574 ms
6  72.14.235.25 (72.14.235.25)  15.590 ms 72.14.223.32 (72.14.223.32)  13.914 ms 72.14.233.39 (72.14.233.39)  14.873 ms
7  72.14.233.39 (72.14.233.39)  14.940 ms 209.85.246.244 (209.85.246.244)  14.376 ms 209.85.246.242 (209.85.246.242)  14.637 ms
8  216.239.41.236 (216.239.41.236)  22.809 ms 209.85.241.1 (209.85.241.1)  23.262 ms 209.85.253.245 (209.85.253.245)  22.780 ms
9  216.239.41.236 (216.239.41.236)  22.690 ms 216.239.42.43 (216.239.42.43)  23.224 ms 216.239.42.37 (216.239.42.37)  23.723 ms
10  * * *
11  * * *
12  wa-in-f104.1e100.net (64.233.184.104)  20.976 ms  20.225 ms  21.688 ms
F9 member since 4 Sep 1999
F9 ADSL customer since 27 Aug 2004
DLM manages your line the same way DRM manages your rights.
Look at all the pretty graphs! (now with uptime logging!)
Community Gaffer
Community Gaffer
Posts: 13,423
Thanks: 1,184
Fixes: 92
Registered: 04-04-2007

Re: Outbound *nix traceroute?

Jumped over to Telehouse North, still the same:
~$ traceroute google.com
traceroute to google.com (212.56.71.20), 30 hops max, 60 byte packets
1  192.168.1.254 (192.168.1.254)  11.833 ms  11.508 ms  11.267 ms
2  lo0-central10.ptn-ag02.plus.net (195.166.128.191)  30.864 ms  30.633 ms  30.406 ms
3  link-a-central10.ptn-gw01.plus.net (212.159.2.132)  30.180 ms  29.953 ms  29.724 ms
4  xe-1-2-0.ptw-cr01.plus.net (212.159.0.112)  29.496 ms  29.272 ms  28.889 ms
5  ae1.pcl-cr01.plus.net (195.166.129.1)  28.514 ms  28.255 ms  28.016 ms
6  * * *
7  * * *
8  * * *
9  * * *

SWMBO is working from home today, so I'm loathe to do any more hopping Grin

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵

Community Veteran
Posts: 5,169
Thanks: 478
Fixes: 20
Registered: 10-06-2010

Re: Outbound *nix traceroute?

$ traceroute google.com
traceroute to google.com (212.56.71.29), 30 hops max, 60 byte packets
1  gateway (192.168.0.1)  3.485 ms  3.755 ms  5.225 ms
2  lo0.14.central14.pcl-bng01.plus.net (195.166.130.142)  14.198 ms  16.104 ms  16.454 ms
3  irb.14.pcl-cr01.plus.net (84.93.249.145)  17.756 ms  18.427 ms  19.846 ms
4  * * *
5  * * *
6  * * *
7  * * *
8  * * *
9  * * *
10  * * *

Looks normal, some servers will not respond to UDP packets, some servers might not respond except for the ports and protocols used by the services they are running.
# traceroute -T -p 443 google.com
traceroute to google.com (212.56.71.20), 30 hops max, 52 byte packets
1  gateway (192.168.0.1)  2.014 ms  3.672 ms  3.863 ms
2  lo0.14.central14.pcl-bng01.plus.net (195.166.130.142)  12.766 ms  13.414 ms  15.508 ms
3  irb.14.pcl-cr01.plus.net (84.93.249.145)  16.179 ms irb.14.pcl-cr02.plus.net (84.93.249.146)  17.282 ms irb.14.pcl-cr01.plus.net (84.93.249.145)  18.403 ms
4  plusnet-lcy3.plus.net (212.56.71.20)  19.540 ms ae2.pcl-cr01.plus.net (195.166.129.6)  22.650 ms  21.127 ms

A 582n router may also mess with certain types of traceroute.
Community Gaffer
Community Gaffer
Posts: 13,423
Thanks: 1,184
Fixes: 92
Registered: 04-04-2007

Re: Outbound *nix traceroute?

Quote from: ejs
Looks normal, some servers will not respond to UDP packets, some servers might not respond except for the ports and protocols used by the services they are running.

Understood. It's just not something I've come across before when diagnosing stuff so it struck me as something that had recently changed. Looks like I'm probably mistaken though so I shall crawl back into my hole Cheesy
Thanks for testing folks.

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵