Copy of an article I wrote on INEX’s own blog for longevity – original published here on April 10 2019.
In this article, we talk about the new route servers that we deployed across all three peering platforms at INEX during February 2019 and, particularly, RPKI support.
Most route server instances at internet exchanges (IXPs) perform prefix filtering based on route/route6 objects published by internet routing registries (IRRDBs). INEX members would be used to creating these through RIPE’s database. However there are many other registries and the data quality of some of these IRRDB objects is often poor, with problems relating to missing, stale and incorrectly duplicated information.
A typical IRRDB entry would resemble the following:
route: 192.0.2.0/24 descr: Example IPv4 route object origin: AS65500 created: 2004-12-06T11:43:57Z last-modified: 2016-11-16T22:19:51Z source: SOME-IRRDB
RPKI is a public key infrastructure framework designed to secure the internet’s routing infrastructure in a way that replaces IRRs with a database where trust is assigned by the resource holder. The equivalent of a route object in RPKI is called a ROA (Route Origin Authorisation). It is a cryptographically secure triplet of information which represents a route, the AS that originates it and the maximum prefix length that may be advertised. An example of an IPv4 and an IPv6 ROA would be:
( Origin AS, Prefix, Max Length ) ( AS65500, 2001:db8::/32, /48 ) ( AS65501, 192.0.2.0/24, /24 )
ROAs are typically created through your own RIR (so, RIPE for most INEX members). These RIRs are called trust anchors in RPKI. RIPE have created an extremely easy wizard for creating ROAs through the LIR Portal.
To implement RPKI in a router, the router needs to build and maintain a table of verified ROAs from the five RIRs/trust anchors. The easiest way of doing this is to use a local cache server which pulls and validates the ROAs from the trust anchors and uses a new protocol called RPKI-RTR to feed that information to routers. Currently there are three validators: RIPE’s RPKI Validator v3; Routinator 3000 from NLnetLabs; and Cloudflare’s GoRTR. INEX currently uses the former two.
RPKI validation of a route against the table of ROAs yields one of three possible results:
- VALID: a ROA exists for the route and both the prefix length is within the allowed range and the origin ASN matches.
- INVALID: a ROA exists for the route but either (or both) the prefix length is outside the allowed range and/or the origin ASN is different.
- UNKNOWN: no ROA exists for the route.
UNKNOWN is a common response as the database has only a fraction of the prefix coverage as IRR databases do. We are now in a multi-year transition from IRR to RPKI route validation while ROAs are created.
As well as RPKI support, we have also upgrading all route servers to Bird v2.
This is a significant rewrite to Bird which, for v1, maintained separate code and daemons for IPv4 and IPv6. Bird v2 merges these code bases and also introduces support for new SAFIs such as l3vpns / mpls.
Overall, the configuration changes required were minimal and INEX continues to run separate daemons of Bird v2 for IPv4 and IPv6 daemons. Route servers are CPU intensive and separate daemons allows for maximum stability, keeps the configuration clean and fits into the existing deployment processes we have built up with IXP Manager.
Route Server Filtering Flow
Our work on the new route servers will be released to the community as part of IXP Manager v5 shortly. The new filtering flow is enumerated below. One of the key new features is that if any route fails a step, we use internal large community tagging to indicate this and the specific reason to our members through the IXP Manager looking glass (more on that later).
- Filter small prefixes (>/24 for IPv4, >/48 for IPv6).
- Filter martian / bogon ranges.
- Sanity check to ensure the AS path has at least one ASN and no more than 64.
- Sanity check to ensure the peer ASN is the same as first ASN in the prefix’s AS path.
- Prevent next-hop hijacking (where a member advertises a route but puts the next hop as another member’s router rather than their own). We do allow same-AS’s to specify their other router(s).
- Filter known transit networks.
- Ensure that the origin AS is in set of ASNs from member’s AS-SET. See below for some additional detail on this.
- RPKI validation. If it is RPKI VALID, accept the route. If it is RPKI INVALID then filter it.
- If the route is RPKI UNKNOWN, revert to standard IRRDB filtering.
Regarding step 7 above, an AS-SET is another type of IRRDB database entry where a network which also acts as a transit provider for other networks can enumerate the AS numbers of those downstream networks. This is something RPKI does not yet support but it is being worked on – see AS-Cones.
Lastly we have enhanced the BGP large community support to allow our members request as-path prepends on announcements to specific members over the route servers. For these and more supported communities, see the INEX route server page here.
Bird’s Eye and the Looking Glass
As well as IXP Manager, INEX has also written and open sourced a secure micro service for querying Bird daemons called Bird’s Eye. IXP Manager uses this to provide a web-based looking glass into our route collectors and servers. We have recently released v1.2.1 of Bird’s Eye which adds support for Bird v2.
We have greatly enhanced IXP Manager’s looking glass to support both Bird v2 and the large communities we use to tag filtered reasons. You can explore any of INEX’s route servers to see this yourself – for example this is route server #1 for IPv4 on INEX LAN1. When members log into IXP Manager they will also find a new Filtered Prefixes tool which will summarise any filtered routes across all 12 of INEX’s route server instances.
We have spoken about this at a number of conferences recently:
- Barry O’Donovan presented this at APRICOT 2019 in Daejeon, South Korea last February. You can download the slides here and watch the video online.
- Barry also presented this during March’s INEX Members’ Meeting in Dublin for which the slides are available here.
- Nick Hilliard presented on this topic at the 34th Euro-IX Forum in Toulouse, France this April – download the slides here.
- Barry presented this at GPF14 in Montréal, Canada during April. Those slides can be downloaded here.