| Revision as of 13:02, 18 January 2008 editThe Anome (talk | contribs)Edit filter managers, Administrators253,417 edits * Routing Assets Database← Previous edit | Revision as of 13:03, 18 January 2008 edit undoThe Anome (talk | contribs)Edit filter managers, Administrators253,417 edits * Teletraffic engineeringNext edit → | ||
| Line 5: | Line 5: | ||
| Route filtering is generally carried out by ISPs for security reasons; for example, upstream ISPs generally only permit each of their transit customers to announce a limited range of IP addresses, to prevent route hijacking attacks from within their customer networks. They are also likely to filter the routes they accept from other interconnected networks, to avoid their customers being the victims of route hijacking attacks from other networks. | Route filtering is generally carried out by ISPs for security reasons; for example, upstream ISPs generally only permit each of their transit customers to announce a limited range of IP addresses, to prevent route hijacking attacks from within their customer networks. They are also likely to filter the routes they accept from other interconnected networks, to avoid their customers being the victims of route hijacking attacks from other networks. | ||
| Route filtering is also done because some routers have an insuffucient amount of ] in which to store the routing tables; as the ] 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 ]s are not available for dropped prefixes, and even if connectivity is maintained, may result in sub-optimal routes by frustrating the ] intentions of the announcing networks. | Route filtering is also done because some routers have an insuffucient amount of ] in which to store the routing tables; as the ] 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 ]s are not available for dropped prefixes, and even if connectivity is maintained, may result in sub-optimal routes by frustrating the ] intentions of the announcing networks. | ||
| == See also == | == See also == | ||
| * ] | * ] | ||
| * ] | * ] | ||
| * ] | |||
| {{Internet-stub}} | {{Internet-stub}} | ||
Revision as of 13:03, 18 January 2008
 | 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. |
In the context of network routing, route filtering is the concept, especially used on the global Internet with BGP, of filtering (removing from your routing table) routes for certain prefixes (destination address ranges). Route filtering can apply both to routes learned from other routers, and routes announced to other routers.
Route filtering is generally carried out by ISPs for security reasons; for example, upstream ISPs generally only permit each of their transit customers to announce a limited range of IP addresses, to prevent route hijacking attacks from within their customer networks. They are also likely to filter the routes they accept from other interconnected networks, to avoid their customers being the victims of route hijacking attacks from other networks.
Route filtering is also done because some routers have an insuffucient 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. |