What is a route server
A route server redistributes BGP routes received from its BGP clients to other clients according to policy. By peering with a route server, customers can avoid separate BGP sessions with all their peers and instead limit the number of sessions to one with each route server.
NIX offers redundant route servers on the NIX1 peering VLAN. Route server configuration is generated by IXP Manager and hence is based on information entered here, allowing IXP Manager to be the centre of our universe.
NIX Route Server Details
| Name | nix-rs1 | nix-rs2 |
|---|---|---|
| ASN | 44997 | 44997 |
| IPv4 | 185.1.55.251 | 185.1.55.252 |
| IPv6 | 2001:7f8:12:1:0:1:4:4997 | 2001:7f8:12:1:0:2:4:4997 |
| Platform | BIRD | BIRD |
Route Server Filtering
The route servers have several filtering mechanisms
Basic filtering blocks RFC1918 address ranges, martian prefixes, and too long and too short routes. IRRDB filtering is also performed by the route server and is mandatory.
Also read: https://www.nix.no/technical-information/manrs/manrs.html
Resource Public Key Infrastructure (RPKI) filtering is achieved with two different clients:
- Routinator 3000 https://github.com/NLnetLabs/routinator
- Cloudflare RPKI Toolkit https://blog.cloudflare.com/cloudflares-rpki-toolkit/
Customer filtering
Controlling outbound routing information can be done by sending BGP communities as follows:
block the announcement of a route to certain peer (0:< Peer AS>)
- announce a route to a certain peer (44997:<Peer AS>)
- block announcement of a route to all peers (0:44997)
- announce a route to all peers (default behaviour)