Thanks worked $ /usr/sbin/traceroute -I 128.0.0.1 traceroute to 128.0.0.1 (128.0.0.1), 30 hops max, 40 byte packets 1 192.168.0.1 (192.168.0.1) 0.750 ms 0.404 ms 0.307 ms 2 82.197.70.2 (82.197.70.2) 1.307 ms 2.384 ms 2.245 ms 3 non-baresi.c4l.co.uk (84.45.110.18) 1.016 ms 1.033 ms 0.967 ms 4 baresi-platini.c4l.co.uk (84.45.90.49) 1.104 ms 1.085 ms * 5 platini-wolverine.c4l.co.uk (84.45.90.70) 2.481 ms 1.945 ms 1.869 ms 6 195.66.225.24 (195.66.225.24) 1.958 ms 2.225 ms 2.051 ms 7 nl-sar.nordu.net (109.105.97.57) 7.742 ms 7.691 ms 7.699 ms 8 GE-1-0-0.3630.JNR02.Asd001A.surf.net (109.105.98.34) 8.472 ms 8.005 ms * 9 128.0.0.1 (128.0.0.1) 8.515 ms 9.541 ms 8.144 ms
On 7 Dec 2011, at 19:54, Stuart Henderson wrote: > Try traceroute -I > > On 2011/12/07 18:38, Colin Johnston wrote: >> However traceroute via VMHOSTS fails but ping works. >> $ /usr/sbin/ping 128.0.24.1 >> 128.0.24.1 is alive >> $ /usr/sbin/traceroute 128.0.24.1 >> traceroute to 128.0.24.1 (128.0.24.1), 30 hops max, 40 byte packets >> 1 192.168.0.1 (192.168.0.1) 1.180 ms 0.465 ms 0.208 ms >> 2 82.197.70.2 (82.197.70.2) 1.706 ms 1.720 ms 2.018 ms >> 3 non-baresi.c4l.co.uk (84.45.110.18) 0.981 ms 1.006 ms 1.001 ms >> 4 baresi-platini.c4l.co.uk (84.45.90.49) 1.495 ms 1.249 ms 1.032 ms >> 5 platini-wolverine.c4l.co.uk (84.45.90.70) 37.445 ms 2.981 ms 2.522 ms >> 6 195.66.225.24 (195.66.225.24) 2.246 ms 2.024 ms 2.018 ms >> 7 nl-sar.nordu.net (109.105.97.57) 7.712 ms 7.609 ms * >> 8 *^C$
