Configuring Martian Addresses

Martian addresses are host or network addresses about which all routing information is ignored. They commonly are sent by improperly configured systems on the network and have destination addresses that are obviously invalid.

In IPv4, the following are the default martian addresses:

• 0.0.0.0/8

• 127.0.0.0/8

• 128.0.0.0/16

• 191.255.0.0/16

• 192.0.0.0/24

• 223.255.255.0/24

• 240.0.0.0/4

To add martian addresses to the list of default martian addresses in the default routing table ( inet.0 ), include the martians statement at the [edit routing-options] hierarchy level. To add martian addresses to the list of default martian addresses in any other routing tables, or to explicitly add martian addresses to the list of default martian addresses in the default routing table ( inet.0 ), include the martians statement:

 [edit routing-options nb  routing-table-name  ]  martians {   destination-prefix match-type <allow>; } 

In destination-prefix , specify the routing destination in one of the following ways:

• network / mask-length ” network is the network portion of the IP address, and mask-length is the destination prefix length.

• default ” If this is the default route to the destination. This is equivalent to specifying the IP address 0.0.0.0/0 .

For more information about match types, see Table 8.14, "Route List Match Types," on page 347.

In match-type , specify the type of match to apply to the destination prefix.

To delete a martian address from within a range of martian addresses, include the allow option in the martians statement. This option removes an exact prefix that is within a range of addresses that has been specified to be martian addresses. To delete a martian address from the default routing table ( inet.0 ), include the martians statement at the [edit routing-options] hierarchy level. To delete a martian address from any other routing tables, or to explicitly delete a martian address from the default routing table ( inet.0 ), include the martians statement at the [edit routing-options rib routing-table-name] hierarchy level.