Differences

This shows you the differences between two versions of the page.

--- peering-toolbox:route_server [2022/08/01 16:25] – [Purpose] philip
+++ peering-toolbox:route_server [2022/08/26 20:04] (current) – [Bogon Filtering] philip
@@ Line 13: / Line 13: @@
 {{:peering-toolbox:nsquared-mesh.png?500| }}
-basically an n-squared mesh.
+where each line represents a BGP session between two IXP members. This is basically an n-squared mesh.
 Introducing a Route Server results in the BGP sessions for each member being with the Route Route Server, meaning that the number of BGP sessions goes up linearly per member (from Route Server point of view).
-{{:peering-toolbox:rs-mesh.png?300| }}
+{{:peering-toolbox:rs-mesh.png?500| }}
 with each member only having to maintain their BGP sessions with the two Route Servers.
@@ Line 41: / Line 41: @@
 Internet Exchange Points often use their Route Servers to implement bogon prefix filtering and bogon AS filtering. While members of IXPs will normally do this if they are following [[https://www.manrs.org/|MANRS]] principles, it is often helpful for the IXP to also implement this via the Route Server in case the member configuration is omitted.
+Bogon prefix filtering means dropping all prefixes which are not used in the public Internet. This includes private, reserved, and unassigned address space.
+Bogon AS filtering means dropping all prefixes originated by Autonomous Systems using private, reserved, or unassigned ASNs.
 ==== Route Origin Validation ====