traceroute via HSO and ping via HSO works fine
mx5:~ colinj$ traceroute 128.0.24.1
traceroute to 128.0.24.1 (128.0.24.1), 64 hops max, 40 byte packets
1 192.168.1.2 (192.168.1.2) 1.891 ms 2.039 ms 2.154 ms
2 par8.the1.hso.uk.com (217.196.224.63) 114.464 ms 35.539 ms 14.999 ms
3 89.248.31.242 (89.248.31.242) 15.774 ms 16.455 ms 19.882 ms
4 eth-1-2-pcr1.the1.hso.uk.com (89.248.31.62) 15.525 ms 17.012 ms 15.600 ms
5 ge-0-2-0.pgr1.the1.hso.uk.com (89.248.31.94) 15.813 ms 15.874 ms 16.129
ms
6 xe-11-2-0-5.lon10.ip4.tinet.net (213.200.77.81) 16.562 ms 18.133 ms
78.399 ms
7 xe-8-2-0.ams10.ip4.tinet.net (213.200.81.145) 36.020 ms 23.055 ms
xe-0-1-0.ams10.ip4.tinet.net (89.149.180.182) 22.630 ms
8 surfnet-gw.ip4.tinet.net (77.67.72.110) 22.627 ms 23.545 ms 40.677 ms
9 128.0.24.1 (128.0.24.1) 31.362 ms 29.991 ms 48.403 ms
mx5:~ colinj$ ping 128.0.24.1
PING 128.0.24.1 (128.0.24.1): 56 data bytes
64 bytes from 128.0.24.1: icmp_seq=0 ttl=56 time=32.222 ms
64 bytes from 128.0.24.1: icmp_seq=1 ttl=56 time=32.443 ms
64 bytes from 128.0.24.1: icmp_seq=2 ttl=56 time=32.778 ms
^C
--- 128.0.24.1 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 32.222/32.481/32.778/0.229 ms
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$
$
Any ideas ?
Colin Johnston
On 5 Dec 2011, at 15:20, Alex Le Heux wrote:
> Dear Colleagues,
>
> The RIPE NCC is aware that 128.0.0.0/16 is configured as a martian by default
> in (some) Juniper OS, even though RFC 5735 and RFC3330 outline that this /16
> should no longer be reserved as specialised address space.
>
> All allocations that were already issued have been exchanged and for now we
> will hold this space in quarantine.
>
> We urge everyone to change the default behaviour of their Juniper routers:
>
> set routing-options martians 128.0.0.0/16 orlonger allow
> set routing-options martians 191.255.0.0/16 orlonger allow
> set routing-options martians 223.255.255.0/24 exact allow
>
> 128.0.0.0/16 has been added to the RIPE NCC's Debogonising Project:
>
> http://www.ris.ripe.net/debogon/
>
> To facilitate testing, the following prefixes are being announced:
>
> prefix pinagble address
>
> 128.0.0.0/16 128.0.0.1
> 128.0.8.0/21 128.0.8.1
> 128.0.24.0/24 128.0.24.1
>
> Best regards,
>
> Alex Le Heux
> Policy Implementation Co-ordinator
> RIPE NCC
>
>
