128.0.0.0/16 configured as martians in some routers
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
Dear Colleagues, The correct prefix and pingable address list for the Debogonising Project is: prefix pinagble address 128.0.0.0/21 128.0.0.1 128.0.24.0/24 128.0.24.1 Our apologies for the oversight. Best regards, Alex Le Heux Policy Implementation Co-ordinator RIPE NCC On Dec 5, 2011, at 16: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
måndagen den 5 december 2011 16.20.27 skrev Alex Le Heux:
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
Maybe atlas could come in handy here? regards, Bengt Gördén Resilans AB
On 05.12.2011, at 16:51, Bengt Gördén wrote
Maybe atlas could come in handy here?
regards,
Bengt Gördén Resilans AB
Bengt, in fact some of our beta testers for "User Defined Measurements" thought so too and started measurements. At the moment the maximum number of probes they can use per measurement is 10. So this is not entirely representative. Plots are "dnsmon" style, so green=good & red=bad. There is more green than red, that is encouraging. Even more encouraging is that probe #899 actually got connectivity today. Congratulations to AS39759 from the beatiful Republic of San Marino! We will work to make a more representative measurement as soon as possible. Daniel
Am 05.12.11 16:20, schrieb Alex Le Heux:
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
Hello, can you confirm that the first two prefixes are propagated as advertised above? I see here:
show ip bgp 128.0.8.0/21 BGP4 : None of the BGP4 routes match the display condition
show ip bgp 128.0.0.0 Network Path *> 128.0.0.0/21 3549 3257 1103 12654 i
From Tinet's route server:
show ip bgp 128.0.0.0 BGP routing table entry for 128.0.0.0/21, version 28585862 Paths: (1 available, best #1, table Default-IP-Routing-Table) Not advertised to any peer 3257 1103 12654
show ip bgp 128.0.8.0 % Network not in table
route-server.as3257.net>show ip bgp 128.0.0.0/16 % Network not in table route-server.as3257.net>show ip bgp 128.0.8.0/21 % Network not in table Best regards, Franz Georg Köhler -- velia.net Internetdienste GmbH * Chemnitzer Str. 22 * 63452 Hanau Geschäftsführer: Franz G. Köhler, Arek Akilli * AG Hanau * HRB 7588 Tel: 06181-1898119 * Fax: 06181-1898117 * e-mail: fgkoehler@velia.net
Hi Alex, In Dayton, Ohio, US, we are not seeing any 128... routes from TWTC (AS 4323). In St. Louis, Ohio, US, we are seeing the 128.0.0.0/21 via Level 3 (AS 3356). David Swafford, Sr. Network Engineer, CareSource On Mon, Dec 5, 2011 at 10:20 AM, Alex Le Heux <alexlh@ripe.net> 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
participants (5)
-
Alex Le Heux -
Bengt Gördén -
Daniel Karrenberg -
David Swafford -
Franz Georg Köhler