This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[routing-wg] 128.0.0.0/16 configured as martian: Please update your routers
- Previous message (by thread): [routing-wg] 128.0.0.0/16 configured as martian: Please update your routers
- Next message (by thread): [routing-wg] 128.0.0.0/16 configured as martian: Please update your routers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tima Maryin
timamaryin at mail.ru
Thu Oct 13 10:07:10 CEST 2011
On 13.10.2011 11:51, Ingrid Wijte 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. > > We are exchanging the allocations that were already issued and for now > we will (temporarily) stop using this specific /16. > > The RIPE NCC is working on this matter. For now, 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 Keep in mind that martians settings are made per table in Junos, so if you have internet inside routing instance you may want to use this command under routing-instance since if you change those settings in inet.0 it won't affect other tables.
- Previous message (by thread): [routing-wg] 128.0.0.0/16 configured as martian: Please update your routers
- Next message (by thread): [routing-wg] 128.0.0.0/16 configured as martian: Please update your routers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]