nanog mailing list archives
Re: 128.0.0.0/16 configured as martians in some routers
From: Joel jaeggli <joelja () bogus com>
Date: Tue, 06 Dec 2011 08:04:01 -0800
On 12/6/11 00:50 , Florian Weimer wrote:
* Alex Le Heux: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.Would someone please clarify the impact? Will it result in a blackhole, or will the entire announcement be suppressed? I suspect the latter, given what we see and what Chris Adams has reported.
http://www.juniper.net/techpubs/en_US/junos10.2/topics/usage-guidelines/routing-configuring-martian-addresses.html
Current thread:
- Re: 128.0.0.0/16 configured as martians in some routers, (continued)
- Re: 128.0.0.0/16 configured as martians in some routers Chris Adams (Dec 05)
- Re: 128.0.0.0/16 configured as martians in some routers Meftah Tayeb (Dec 05)
- Re: 128.0.0.0/16 configured as martians in some routers Kyle Duren (Dec 05)
- Re: 128.0.0.0/16 configured as martians in some routers Jack Bates (Dec 05)
- Re: 128.0.0.0/16 configured as martians in some routers Chris Adams (Dec 05)
- RE: 128.0.0.0/16 configured as martians in some routers John van Oppen (Dec 05)
- Re: 128.0.0.0/16 configured as martians in some routers Chris Adams (Dec 05)
- RE: [ncc-announce] 128.0.0.0/16 configured as martians in some routers Eric Tykwinski (Dec 09)
- Re: [ncc-announce] 128.0.0.0/16 configured as martians in some routers Meftah Tayeb (Dec 09)
- Re: 128.0.0.0/16 configured as martians in some routers Mark Tinka (Dec 06)
- Re: 128.0.0.0/16 configured as martians in some routers Joel jaeggli (Dec 06)
- Martian 128.0.0.0/16 - Fixed Releases in Junos Mark Tinka (Dec 07)