This is an old revision of this page, as edited by Jec (talk | contribs) at 04:16, 16 December 2008 (→Security resons). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 04:16, 16 December 2008 by Jec (talk | contribs) (→Security resons)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)This article needs attention from an expert in Computer networking. Please add a reason or a talk parameter to this template to explain the issue with the article. WikiProject Computer networking may be able to help recruit an expert. (November 2008) |
In the context of network routing, route filtering is the process by which certain routes are not considered for inclusion in the local route database, or not advertised to one's neighbours. Route filtering is particularly important for BGP on the global Internet, where it is used for a variety of reasons.
Types of filtering
There are two times when a filter can be naturally applied: when learning routes from a neighbour, and when announcing routes to a neighbour.
Input filtering
In input filtering, a filter is applied to routes as they are learned from a neighbour. A route that has been filtered out is discarded straight away, and hence not considered for inclusion into the local routing database.
Output filtering
In output filtering, a filter is applied to routes before they are announced to a neighbour. A route that has been filtered out is never learned by a neighbour, and hence not considered for inclusion in the remote route database.
Reasons to filter
Economic reasons
When a site is multihomed, announcing non-local routes to a neighbour different from the one it was learned from amounts to advertising the willingness to serve for transit, which is undesirable unless suitable agreements are in place. Applying output filtering on these routes avoids this issue.
Security resons
An upstream ISP will typically perform input filtering on routes learned from a customer to restrict them to the addresses actually assigned to that customer. Doing so makes address hijacking more difficult.
Technical reasons
Route filtering is also done because some routers have an insufficient amount of RAM in which to store the routing tables; as the global BGP table has grown, older routers (or any router running out of RAM) must filter routes in order to keep from running out of RAM (and crashing). This is usually done by removing of a route for any prefix more specific than a certain length (anything more specific than a /24, for example). This is not an ideal practice, as it may result in loss of connectivity if less-specific covering routes are not available for dropped prefixes, and even if connectivity is maintained, may result in sub-optimal routes by frustrating the traffic engineering intentions of the announcing networks.
See also
This Internet-related article is a stub. You can help Misplaced Pages by expanding it. |
This article related to telecommunications is a stub. You can help Misplaced Pages by expanding it. |