Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Alex Atkin UK]

Got an interesting comparison here from some traceroutes to bbc.co.uk.

Code: [Select]

Three 5G:
 1  192.168.8.1 (192.168.8.1)  0.283 ms  0.345 ms  0.234 ms
 2  * * *
 3  172.25.211.5 (172.25.211.5)  12.230 ms  17.168 ms  12.542 ms
 4  * * *
 5  * * *
 6  172.25.216.93 (172.25.216.93)  24.878 ms  26.740 ms  28.991 ms
 7  * * *
 8  172.25.195.146 (172.25.195.146)  16.855 ms  16.718 ms  14.491 ms
 9  167.82.128.245 (167.82.128.245)  19.996 ms  18.236 ms  16.485 ms
10  * * *
11  151.101.128.81 (151.101.128.81)  22.132 ms  20.697 ms  17.495 ms

Code: [Select]

Vodafone 4G (Lebara):
 1  192.168.9.1 (192.168.9.1)  0.868 ms  0.705 ms  1.008 ms
 2  * * *
 3  192.168.213.21 (192.168.213.21)  42.550 ms  37.688 ms  33.004 ms
 4  192.168.213.22 (192.168.213.22)  29.953 ms  40.806 ms  39.018 ms
 5  * * *
 6  * * *
 7  63.130.105.110 (63.130.105.110)  42.584 ms  37.884 ms  37.858 ms
 8  90.255.251.119 (90.255.251.119)  37.018 ms  39.731 ms  40.025 ms
 9  151.101.0.81 (151.101.0.81)  27.631 ms  38.139 ms  37.860 ms

Code: [Select]

Traceroute to AAISP L2TP server over Vodafone 4G:
 1  192.168.9.1 (192.168.9.1)  0.584 ms  0.571 ms  0.952 ms
 2  * * *
 3  192.168.213.21 (192.168.213.21)  47.826 ms  38.802 ms  29.976 ms
 4  192.168.213.22 (192.168.213.22)  41.072 ms  40.618 ms  29.980 ms
 5  * * *
 6  * * *
 7  63.130.105.130 (63.130.105.130)  40.762 ms  30.094 ms  44.953 ms
 8  lonap.n.aimless.thn.aa.net.uk (5.57.80.69)  37.034 ms  44.815 ms
    a.linx.thn.aaisp.net.uk (195.66.225.47)  38.011 ms
 9  l2tp.thn.aa.net.uk (90.155.53.19)  44.639 ms  30.828 ms  37.892 ms

Code: [Select]

Traceroute OVER the L2TP tunnel on Vodafone 4G to bbc.co.uk:
 1  l2tp.thn.aa.net.uk (90.155.53.19)  25.206 ms  22.048 ms  24.424 ms
 2  k-aimless.thn.aa.net.uk (90.155.53.101)  27.985 ms  28.277 ms  26.497 ms
 3  195.66.225.91 (195.66.225.91)  20.012 ms  23.739 ms  24.540 ms
 4  151.101.64.81 (151.101.64.81)  26.440 ms  22.719 ms  24.543 ms
Say what now?  Its LOWER than the traceroute TO the L2TP server yet its going to that server and then onwards to bbc 

Code: [Select]

And for comparison, Zen over VDSL:
 1  vt1.cor1.lond1.ptn.zen.net.uk (51.148.72.21)  13.105 ms  13.157 ms  13.249 ms
 2  lag-8.p1.thn-lon.zen.net.uk (51.148.73.158)  13.293 ms  13.552 ms  13.408 ms
 3  lag-1.br1.thn-lon.zen.net.uk (51.148.73.153)  13.645 ms  13.063 ms  12.809 ms
 4  ip81-59.fastly-gw1.lonap.net (5.57.81.59)  12.737 ms  12.794 ms  12.688 ms
 5  151.101.192.81 (151.101.192.81)  12.791 ms  12.847 ms  12.790 ms
I also notice Vodafone aren't using the proper CG-NAT IP range and instead using a private LAN range, that seems naughty and asking for trouble.

[Reformed]

I'm not sure what you're trying to say here? A reminder network paths can be asymmetrical and that responding to your traceroute may end up in the management plane while sending onwards to the next hop will be in the forwarding plane. The software and hardware may be quite different.

[aesmith]

I've often seen traceroute showing longer RTT on intermediate hops.  Do you get the same figures if you ping each of those intermediates?  I also wonder whether some kit, having better things to do, doesn't put a high priority in sending ICMP TTL exceeded messages.

[Alex Atkin UK]

Its not that it was a surprise, its just I have a page that shows my modem stats and does traceroutes out each link and was revising it so thought the results were interesting.

People new to networking often think traceroute/ping is gospel, when we of course know its far from the truth and at best a rough guideline only.

[jelv]

Do you get the same figures if you ping each of those intermediates?

I'm surprised how infrequently we see the Windows pathping utility used which does that for you:

C:\Users\John>pathping -4 bbc.co.uk

Tracing route to bbc.co.uk [151.101.64.81]
over a maximum of 30 hops:
  0  Elvin11.fritz.box [192.168.1.111]
  1  fritz.box [192.168.1.1]
  2  vt1.cor1.lond1.ptn.zen.net.uk [51.148.72.21]
  3  lag-8.p1.thn-lon.zen.net.uk [51.148.73.158]
  4  lag-1.br1.thn-lon.zen.net.uk [51.148.73.153]
  5  ip81-59.fastly-gw1.lonap.net [5.57.81.59]
  6  151.101.64.81

Computing statistics for 150 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Elvin11.fritz.box [192.168.1.111]
                                0/ 100 =  0%   |
  1    3ms     0/ 100 =  0%     0/ 100 =  0%  fritz.box [192.168.1.1]
                                0/ 100 =  0%   |
  2   13ms     0/ 100 =  0%     0/ 100 =  0%  vt1.cor1.lond1.ptn.zen.net.uk [51.148.72.21]
                                0/ 100 =  0%   |
  3  ---     100/ 100 =100%   100/ 100 =100%  lag-8.p1.thn-lon.zen.net.uk [51.148.73.158]
                                0/ 100 =  0%   |
  4   15ms     0/ 100 =  0%     0/ 100 =  0%  lag-1.br1.thn-lon.zen.net.uk [51.148.73.153]
                                0/ 100 =  0%   |
  5  ---     100/ 100 =100%   100/ 100 =100%  ip81-59.fastly-gw1.lonap.net [5.57.81.59]
                                0/ 100 =  0%   |
  6   13ms     0/ 100 =  0%     0/ 100 =  0%  151.101.64.81

Trace complete.

[Alex Atkin UK]

I have to do it from pfSense due to multi-WAN, I have to specify the gateway.

Of course I could cycle the gateways on a client but the idea here is at a glance I get a rough look at the health of my WANs.