Martian addresses are not routable and the routes, which are considered as Martians, cannot be installed in the routing table.

With RFC 5735 in effect, the 128.0.0.0/16, 191.255.0.0/16, and 223.255.255.0/24 routes are no longer Martian and they can be allocated to users via the Regional Internet Registry (RIR).

For Junos OS versions that were released before November 21, 2011, the default Martian routes are as follows:

The 128.0.0.0/16, 191.255.0.0/16, and 223.255.255.0/24 addresses should be set to allowed in the Martian routes.

According to RFC 5735 , which obsoletes RFC 3330 , the 128.0.0.0/16, 191.255.0.0/16, and 223.255.255.0/24 addresses can now be allocated by the Regional Internet Registry (RIR) to users. Because of this, they have to be removed from the default Martian routes in Junos. Junos releases after November 21, 2011, accompany these changes. For more information, refer to PSN-2011-10-393 and PR698121 .

To allow the 128/16, 191.255/16, and 223.255.255/24 routes in the Martian routes, the following commands can be used:

[edit routing-options martians]
root@my-srx# show | display set
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 orlonger allow [edit]
root@my-srx# run 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 -- allowed
191.255.0.0/16 orlonger -- allowed
192.0.0.0/24 orlonger -- disallowed
223.255.255.0/24 orlonger -- allowed
240.0.0.0/4 orlonger -- disallowed

These commands have to be included in all routing-instance sections:

[edit routing-instances VR1 routing-options martians]
root@my-srx# show | display set
set routing-instances VR1 routing-options martians 128.0.0.0/16 orlonger allow
set routing-instances VR1 routing-options martians 191.255.0.0/16 orlonger allow
set routing-instances VR1 routing-options martians 223.255.255.0/24 orlonger allow 

You can use an apply-group to ease the configuration:

set groups rfc-5735 routing-instances <*> routing-options martians 128.0.0.0/16 orlonger allow
set groups rfc-5735 routing-instances <*> routing-options martians 191.255.0.0/16 orlonger allow
set groups rfc-5735 routing-instances <*> routing-options martians 223.255.255.0/24 orlonger allow
set apply-groups rfc-5735

These routes can then be successfully installed in the routing table.

• PR698121 - 128/16 is not a martian anymore
• KB15067 - Commit fails with the error message "Invalid ipv4 address entry". [juniper.net]