Hi Aleksander,
Martians are prefixes for which routing information will never be
accepted. They also are never used for OSPF or BGP RIDs.
If you have a default route, you will still forward traffic according to
that route table entry, even if the destination address falls in Martian
space.
Declaring a prefix to be a Martian does not imply that firewall
filtering is done on that prefix. If you have a default route and you
also want the 20/8 space to be dropped, you would need to do that
separately.
To my knowledge, it would be relatively uncommon to declare a prefix
like 20/8 to be a Martian. Even RFC1918 addresses are not Martians by
default.
For more details on the Juniper implementation, see:
https://www.juniper.net/techpubs/software/junos51/swconfig51-routing/html/routing-tables-config48.html#1015154
HTH,
Scott
> Aleksander Zawisza wrote:
>
> How does Juniper treat traffic destined for martian addresses? Here's
> the scenario: I'm sending traffic to a router that has a default route
> out. The traffic has a destination address of 20.20.20.2. On the
> router with the default route, I set a martian for 20.0.0.0/8
> orlonger. Is the Juniper supposed to drop the traffic since the
> destination network is a martian, or do martians only apply to
> receiving routes, not to traffic?
>
> I tried this in the lab, and the Juniper still forwards the "martian
> traffic" out its default interface. Which document is this behaviour
> standardized in, for reference?
>
> Regards,
>
> Aleksander Zawisza
> Nortel Networks, Juniper Global Networks Product Support
> ' Juniper GNPS Hotline: 1-800-4NORTEL (919-905-4210) / Support: ERC
> 577 / Hardware: ERC 578
> ( 613-768-4089 / ESN 398-4089
> * zawisza@nortelnetworks.com
> : http://juniper.ca.nortel.com
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:38 EDT