[j-nsp] JUNOS and 128.0.0.0 martian (JFYI)

[Graham Brown]

Hello Tima,

Thank you for making me aware of this and raising this with JTAC, I am sure
that this would be deemed as critical and an easy fix. If you get allocated
a PR, could you please share this with the group so we can monitor the
progress and get a heads up on what releases contain the fix. I am sure that
this will get flagged as a fix rather than a feature request, which would
generally follow a longer path for implementation.

Thank you,
Graham

On Mon, Oct 10, 2011 at 1:39 PM, Tima Maryin <timamaryin at mail.ru> wrote:

> Hello!
>
>
> Recently RIPE NCC started to allocate addresses from 128/8 to end users,
> example:
>
> https://apps.db.ripe.net/**whois/lookup/ripe/inetnum/128.**
> 0.0.0-128.0.7.255.html<https://apps.db.ripe.net/whois/lookup/ripe/inetnum/128.0.0.0-128.0.7.255.html>
>
>
> Junos software (upto and including 11.1) blocks those address by default:
>
> > show route martians
>
> inet.0:
>             0.0.0.0/0 exact -- allowed
>             0.0.0.0/8 orlonger -- disallowed
>             127.0.0.0/8 orlonger -- disallowed
>             128.0.0.0/16 orlonger -- disallowed
>
>
> In fact there will be no connectivity for new addresses and Juniper routers
> all around the world unless people change de.fault behavior or juniper
> change default settings for martians
>
> I think it's time to do, I've just open JTAC case about it.
>
>
>
> p.s. set routing-options martians 128.0.0.0/16 orlonger allow
> fixes it.
> ______________________________**_________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/**mailman/listinfo/juniper-nsp<https://puck.nether.net/mailman/listinfo/juniper-nsp>
>