Child pages
  • BGP Route Collector
Skip to end of metadata
Go to start of metadata


 

Each INX peering LAN has a BGP route collector.  A BGP session with the collector is pre-configured for each peer.  Peering sessions to route-collectors are done in advance of port turn-up, and set to passive, so we will automatically respond to, and activate peering sessions from active participants.  BGP prefix information gathered via this service, is made available via the Looking Glass as a diagnostics tool for the Internet community.  We heartily encourage all peers to peer with the route-collector at each of the INXes that they are present at.

 

No advertised prefixes

Under normal operating conditions, the route-server does not advertise any prefixes to its peers.


LocationASNHostnameIPv4IPv6
JINX37474routecollector.jinx.net.za196.223.14.32001:43f8:1f0::3
CINX37663routecollector.cinx.net.za196.223.22.32001:43f8:1f1::3
DINX37668routecollector.dinx.net.za196.223.30.32001:43f8:1f2::3

ASN Uniqueness

We use distinctly separately ASNs for the route-collector and the BGP route servers, as we expect that for their own purposes, not all peers will want to peer with the BGP route servers.  While we would prefer to use a completely separate ASN for this, AfriNIC would not allocate us a third ASN explicitly for this purpose, so we are re-using the AS number that we use for each of the INX management networks.



The BGP route collector is a list of potential routes that are available at that specific IX.  It's important to note that not all of these might be available to you, depending on the peers that you have, and the particular policy that is in place between you.

 

Filter free

The route-servers do not perform any filtering of sort of prefix filtering for prefixes that we receive from peers. This makes it an excellent tool to spot configuration issues from a neutral, 3rd party perspective.