for example
https://apps.db.ripe.net/whois/lookup/ripe/inetnum/128.0.0.0-128.0.7.255.html
Take a look at RFC5735 which obsoletes RFC3330.
So if you have it as martians, you possibly cannot route to that remote subnets. Also transit ISPs should change this if they dont route them.
Workaround - Deleting Martian Addresses:
http://www.juniper.net/techpubs/en_US/junos10.2/topics/usage-guidelines/routing-configuring-martian-addresses.html#id-10349412
source: http://puck.nether.net/lists/juniper-nsp/0319.html
UPDATE!!!:
> https://apps.db.ripe.net/whois/lookup/ripe/inetnum/128.0.0.0-128.0.7.255.html
skip
> p.s. set routing-options martians 128.0.0.0/16 orlonger allow
> fixes it.
Couple updates about it.
martians are per table in Junos, so if you run internet in vrf (yes,
there are such people!) you need to use that command per routing instance.
RIPE NCC was awared about this issue and now reallocate blocks to those
who got addrs from 128.0.0.0/16
https://apps.db.ripe.net/whois/lookup/ripe/inetnum/128.0.0.0-128.0.7.255.html
IANA changed it. there was mail.ru now there is nothing
No comments:
Post a Comment