Traceroute

[Ted]

If the router uses busybox it will use a linux command from the GUI.

Yes, never thought of that.

Rik, could you run a traceroute from your 2700 and see what hapens?

[Steve]

Is this another example of Windows perhaps showing things to be something they are not i.e the traceroute to IDNet will not complete on other OSs and the disparency in ping times between XP and the rest.

[mchunt_idnet]

The Letchworth power issue only affects our 01462 480092 incoming number (due to our ISDN30 & PBX being hosted there) and a few very old websites (classic ASP) - no ADSL traffic goes anywhere near Letchworth.

If you can reach it, I wouldn't worry. It's possible the power outage at Letchworth is affecting it, but it should also affect me.

[Simon]

Thanks, Martin. 

[mchunt_idnet]

I also have the same problem when using xUbuntu using the default traceroute options

traceroute www.idnet.net
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  11.612 ms  11.748 ms  11.870 ms
2  telehouse-gw4-lo2.idnet.net (212.69.63.99)  29.708 ms  29.839 ms  30.021 ms
3  telehouse-gw3-g0-1-400.idnet.net (212.69.63.243)  30.221 ms  30.350 ms  30.439 ms
4  redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1)  39.126 ms  39.232 ms  39.360 ms
5  redbus-gw1-fa2-0-300.idnet.net (212.69.63.225)  37.916 ms  38.114 ms  38.246 ms
6  * * *
7  * * *
8  * * *
9  * * *

If however I force the linux traceroute command to use ICMP I get

traceroute www.idnet.net -I
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  9.545 ms  9.787 ms *
2  * * *
3  * * *
4  * * *
5  * * *
6  * www.idnet.net (212.69.36.10)  43.566 ms  43.631 ms

If I then restrict the number of simultaneous probe packets I get the expected results

traceroute www.idnet.net -I -N 1
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  9.582 ms  6.426 ms  10.505 ms
2  telehouse-gw4-lo2.idnet.net (212.69.63.99)  29.142 ms  29.713 ms  30.416 ms
3  telehouse-gw3-g0-1-400.idnet.net (212.69.63.243)  29.264 ms  29.673 ms  30.396 ms
4  redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1)  29.247 ms  29.629 ms  30.431 ms
5  redbus-gw1-fa2-0-300.idnet.net (212.69.63.225)  29.217 ms  29.773 ms  30.402 ms
6  www.idnet.net (212.69.36.10)  29.233 ms  29.319 ms  29.800 ms

[Ted]

I also have the same problem when using xUbuntu using the default traceroute options

traceroute www.idnet.net
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  11.612 ms  11.748 ms  11.870 ms
2  telehouse-gw4-lo2.idnet.net (212.69.63.99)  29.708 ms  29.839 ms  30.021 ms
3  telehouse-gw3-g0-1-400.idnet.net (212.69.63.243)  30.221 ms  30.350 ms  30.439 ms
4  redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1)  39.126 ms  39.232 ms  39.360 ms
5  redbus-gw1-fa2-0-300.idnet.net (212.69.63.225)  37.916 ms  38.114 ms  38.246 ms
6  * * *
7  * * *
8  * * *
9  * * *

If however I force the linux traceroute command to use ICMP I get

traceroute www.idnet.net -I
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  9.545 ms  9.787 ms *
2  * * *
3  * * *
4  * * *
5  * * *
6  * www.idnet.net (212.69.36.10)  43.566 ms  43.631 ms

If I then restrict the number of simultaneous probe packets I get the expected results

traceroute www.idnet.net -I -N 1
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  9.582 ms  6.426 ms  10.505 ms
2  telehouse-gw4-lo2.idnet.net (212.69.63.99)  29.142 ms  29.713 ms  30.416 ms
3  telehouse-gw3-g0-1-400.idnet.net (212.69.63.243)  29.264 ms  29.673 ms  30.396 ms
4  redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1)  29.247 ms  29.629 ms  30.431 ms
5  redbus-gw1-fa2-0-300.idnet.net (212.69.63.225)  29.217 ms  29.773 ms  30.402 ms
6  www.idnet.net (212.69.36.10)  29.233 ms  29.319 ms  29.800 ms

Just using the -I switch (Use ICMP ECHO for probes) works for me, without limiting the amount of probe packets sent.

[root@MDK2010 ted]# traceroute www.idnet.net -I
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1  homeportal (192.168.1.254)  6.830 ms  6.830 ms  6.815 ms
2  telehouse-gw2-lo1.idnet.net (212.69.63.51)  56.054 ms  56.103 ms  65.995 ms
3  telehouse-gw3-g0-1-400.idnet.net (212.69.63.243)  67.845 ms  67.886 ms  77.608 ms
4  redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1)  93.440 ms  95.538 ms  95.581 ms
5  redbus-gw1-fa2-0-300.idnet.net (212.69.63.225)  79.591 ms  84.030 ms  85.572 ms
6  www.idnet.net (212.69.36.10)  85.565 ms  68.795 ms  70.787 ms

[Ted]

Just ran a tracert on my daughters Vista laptop "cough, spit" and it completed with no issue.

Would appear to be a "unix" anomaly! 

[Rik]

I won't bother then, Ted. Thanks for the info, Martin.

[Steve]

Thanks Martin, I suppose if we need to remember to use the switches.