CNX offers connected networks the opportunity to peer via its route servers, thus helping to reduce the complexity of your peering. However you should still
maintain your peering relationships and peering polices! CNX is not responsible for any impact on traffic flow due to policies configured at RS by other members.
Our RS just makes it easier to connect to everyone.
Normally, you need to maintain separate BGP sessions to each of your peers’ routers. With a route server you can replace all or a subset of these sessions with one session towards each route server. CNX operates 2 route-servers (RS) at each location.
The route servers do not partake in the forwarding path, so they do not forward any traffic. Peering with a route server does not mean that you must accept routes from all other route server participants, you are free to filter routes or peers where you have a direct peering agreement.
Please contact us to setup the BGP session with RS.
Route Server details
Our route servers support IPv4, IPv6 and 4byte ASNs.
Peering point Sabay Digital, #308 Monivong
|Peering Network ipv4||184.108.40.206/26|
|Peering Network ipv6||2001:DE8:1D::/64|
Peering point Psa Depot (obsolete only for old peers at BSS)
|Peering Network ipv4||220.127.116.11/26|
|Peering Network ipv6||2001:DE8:1D:1::/64|
when peering with our RS, please note
- You must peer with both RS and advertise the same amount and length of prefixes for resilience
- Only your own ASN and ASN’s that you listed as downstream are accepted by the RS
- You can only advertise prefixes assigned to you or your downstream peers
- Disable check on first-ASN, this is applicable to Huawei (“undo check-first-as”) and Cisco equipment (“no bgp enforce-first-as”)
- CNX RS will deny all network updates with a network mask length greater than /24.
- The RS only accept a maximum of 1,000 prefixes, please contact us if you are advertising more than that
- the route servers are set to passive mode and will never initiate a BGP session. You should make sure that your equipment does so, i.e. connects to our TCP port 179 and that your inbound filtering/ACL rules permit established sessions with the route servers.