[Contents] [Prev] [Next] [Index] [Report an Error]


Configure 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:

In IPv6, the loopback address, the reserved and unassigned prefixes from RFC 2373, and the link-local unicast prefix are the default martian addresses.

Add Martian Addresses

To add martian addresses to the list of default martian addresses in the default IPv4 routing table (inet.0), include the martians statement at the [edit routing-options] hierarchy level (for routing instances, include the statements at the [edit routing-instances routing-instance-name routing-options] hierarchy level):

[edit]
routing-options {
    martians { 
        destination-prefix match-type; 
    }
}

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

[edit]
routing-options {
    rib inet6.0 {
        martians {
            destination-prefix match-type; 
        }
    }
}

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 at the [edit routing-options rib rib-table] hierarchy level (for routing instances, include the statement at the [edit routing-instances routing-instance-name routing-options rib rib-table] hierarchy level):

[edit]
routing-options {
    rib routing-table-name {
        martians {
            destination-prefix match-type; 
        }
    }
}

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

In match-type, specify the type of match to apply to the destination prefix. For more information about match types, see the JUNOS Internet Software Configuration Guide: Policy Framework.

Remove Martian Addresses

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 (for routing instances, include the statements at the [edit routing-instances routing-instance-name routing-options] hierarchy level):

[edit]
routing-options {
    martians { 
        destination-prefix match-type allow; 
    }
}

To delete a martian address from other routing tables, or to explicitly delete a martian address from the primary IPv6 routing table (inet6.0), include the martians statement at the [edit routing-options rib inet6.0] hierarchy level:

[edit]
routing-options {
    rib inet6.0 {
        martians {
            destination-prefix match-type allow; 
        }
    }
} 

[Contents] [Prev] [Next] [Index] [Report an Error]