Differences

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

--- peering-toolbox:route_collector [2022/07/31 17:46] – [Implementation] philip
+++ peering-toolbox:route_collector [2022/07/31 17:50] – [Implementation] philip
@@ Line 25: / Line 25: @@
 {{:peering-toolbox:routecollector.png?300| }}
+===== Technical Details =====
+The Route Collector will usually operate in a private Autonomous System. There is no need for a public ASN as the Collector is not involved in any BGP policy, nor is it providing any transit to any other network.
+The device used can be quite simple. A Linux or BSD container is sufficient, as long as it can run the BGP daemon and has enough memory to hold the IXP's routes. There is no packet forwarding requirement.
+The Collector is usually configured with a 2nd ethernet interface, for the backend connection to the IXP Services LAN. This is so that it can be used for the IXP's Looking Glass and accessed directly rather than over the IXP fabric itself. If a 2nd interface is configured, packet forwarding needs to be disabled (the default) so that IXP members aren't able to send traffic over the collector into the IX's Services transit network.
 [[:peering-toolbox/peering-technologies| Back to "Peering Technologies" page]]