mailing list archives
Re: 220.127.116.11/16 configured as martians in some routers
From: David Swafford <david () davidswafford com>
Date: Tue, 6 Dec 2011 06:16:10 -0500
In Dayton, Ohio, US, we are not seeing any 128... routes from TWTC (AS 4323).
In St. Louis, Ohio, US, we are seeing the 18.104.22.168/21 via Level 3 (AS 3356).
Sr. Network Engineer, CareSource
On Mon, Dec 5, 2011 at 10:20 AM, Alex Le Heux <alexlh () ripe net> wrote:
The RIPE NCC is aware that 22.214.171.124/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 126.96.36.199/16 orlonger allow
set routing-options martians 188.8.131.52/16 orlonger allow
set routing-options martians 184.108.40.206/24 exact allow
220.127.116.11/16 has been added to the RIPE NCC's Debogonising Project:
To facilitate testing, the following prefixes are being announced:
prefix pinagble address
Alex Le Heux
Policy Implementation Co-ordinator
RE: [ncc-announce] 18.104.22.168/16 configured as martians in some routers Eric Tykwinski (Dec 09)
Re: 22.214.171.124/16 configured as martians in some routers Florian Weimer (Dec 06)
Re: 126.96.36.199/16 configured as martians in some routers David Swafford (Dec 07)
- Re: 188.8.131.52/16 configured as martians in some routers, (continued)