RFC 3704:Ingress Filtering for Multihomed Networks
RFC-Ref

default route


Click on the red underlined text to get to the source

... o Loose Reverse Path Forwarding ignoring default routes Other mechanisms are also possible, and indeed, there are a number of ...
... RPF, but differs in that it checks only for the existence of a route (even a default route, if applicable), not where the route points to. Practically, this could be considered as a "route ...
... Also, many ISPs use default routes for various purposes such as collecting illegitimate traffic at so-called "Honey Pot" systems or ...
... route to, and smaller ISPs may well purchase transit capabilities and use a default route from a larger provider. At least some implementations of Loose RPF ...
... provider. At least some implementations of Loose RPF check where the default route points to. If the route points to the interface ...
... RPF interface even in the presence of a default route. If such fine-grained checking is not implemented, presence of a default route ...
... interface even in the presence of a default route. If such fine-grained checking is not implemented, presence of a default route nullifies the effect of Loose RPF completely. ...
... Loose Reverse Path Forwarding Ignoring Default Routes ...
... The fifth implementation technique may be characterized as Loose RPF ignoring default routes, i.e., an "explicit route presence check". In this approach, the router ...
... route is found. However, in the lookup, default routes are excluded. Therefore, the technique is mostly usable in scenarios where default routes are used only to ...
... lookup, default routes are excluded. Therefore, the technique is mostly usable in scenarios where default routes are used only to catch traffic with bogus source addresses ...



Google
Web
RFC-Ref