There are two BGP separate route servers on each peering LAN. It is recommended to always peer with both BGP Route Servers at a location, as sessions to both servers ensure that there is no disruption to the advertisement of your prefixes should it be necessary to performance maintenance on a Route Server. The Route Servers do not peer with each other by design, so peering with only one server is an unnecessary risk for your network!
Bi-lateral peering is considered best practice !
While the BGP Route Server service is made available as a convenience, it is strongly recommended that, in addition to any sessions you plan to establish with the BGP Route Servers, you still maintain direct bi-lateral peering sessions with peers that you feel are important to your network! BGP Route Servers should be used to pickup quick/easy/additional peers only, and not as a replacement for your discrete peering policy!
In particular there are many peers that advertise only a subset of their prefixes to the BGP Route Server. Always aim for a bilateral session !
First ASN Check
Remember that the BGP-RS service at all the INXes do not include the BGP-RS ASN in BGP update messages, as the RS is not actually a transit network. Ensure that if you do plan on peering with the BGP Route Servers, you understand that the BGP-RS does not attach its ASN to outbound BGP messages.
Please implement the IOS "
no bgp enforce-next-as" (or IOS-XR "
enforce-first-as disable"), or appropriate equivalent, for your platform.
Filtering policy and process
INX has always believed in filtering and we filter all client sessions to the BGP-RS service. We encourage peers to keep their IRR objects accurate to help us to autogenerate these filters.
- Filters are built based on RPKI and IRRDB registered objects.
- We search the AfriNIC, RADB and RIPE registries (in that order).
- We permit only exact match filters for both IPv4 and IPv6.
- RPKI invalids are dropped.
- Some prefixes are automatically filtered by the route servers (eg. bogons and martians).
- We do not accept BGP announcements from private ASNs, or with private ASNs in the path.
INX's Route Server filtering policy is below:
- Drop small prefixes – longer than /24 for ipv4 and longer than /48 for ipv6.
- Drop all well-known martians and bogons.
- Ensure that there is at least 1 ASN and less than 64 ASNs in the AS path.
- Ensure that the peer AS is the same as the first AS in the AS path.
- Drop any prefix where the next-hop IP address is not the same as the peer IP address. This prevents prefix hijacking.
- Drop any prefix with a transit network ASN in the AS path.
- Ensure that origin AS is in set of ASNs from the client’s IRRDB AS-SET.
- If the prefix is evaluated as RPKI valid, accept.
- If the prefix is evaluated as RPKI invalid, drop.
- If the prefix is evaluated as RPKI unknown, revert to standard IRRDB prefix filtering.
Filter generation happens every 4h starting at 0h45. If you need a filter update done in an emergency, please call, or email us, using the details on the INX support page.
BGP Communities for policy control
A simple set of BGP communities are made available for rudimentary policy control. These will be expanded on over time, as the BGP Route Server service is enhanced. We provide both extended and large community (RFC 8092) support. Note that if you intend to effect policy to 32bit ASNs you'll need to make use of the BGP-LC communities. As a general rule, you should implement large community (LC) filtering if your device supports this. Do not mix both types!
Remember to use the correct ASN
|0:peer-asn||deny to peer-asn||block announcement of prefix to peer-as|
|0:37700||block all||block announcement of prefix to all peers|
|37700:peer-asn||allow to peer-asn||announce prefix to specific peer-as (in conjunction with block all)|
|37700:37700||allow all||announce prefix to all peers (implicit default)|
We honour the well-known no-export and no-advertise communities as if they were sent to us as a regular peer. If you would specifically like us to propagate these, then please tag as below:
|37700:65281||add no-export||adds the well known no-export community to all routes sent to peers|
|37700:65282||add no-advertise||adds the well known no-advertise community to all routes sent to peers|
BGP Large Community Support for policy control
|37700:0:peer-asn||deny to peer-asn||block announcement of prefix to peer-asn|
|37700:0:0||block all||block announcement of prefix to all peers|
|37700:1:peer-asn||allow to peer-as||announce prefix to specific peer-as (in conjunction with block all)|
|37700:1:0||allow all||announce prefix to all peers (implicit default)|
We also support path prepending using the following policy:
|37700:101:peer-asn||Prepend to peer AS once|
|37700:102:peer-asn||Prepend to peer AS twice|
|37700:103:peer-asn||Prepend to peer AS three times|
Communities returned for filtered routes
If your prefix is filtered by the BGP-RS, we'll return one of the BGP communities below, that should help aid in the debugging process.
Prefixes auto-filtered by the Route Servers
For the overall safety and security of our participants, we actively filter the following prefixes at the Route Servers. That is, advertisements from peers, containing the following networks, will be dropped, and not onward announced.
ASNs filtered by the Route Servers (Tier-1 networks/peer-locking)
We filter a regular set of networks that are known to be transit-free (ie. we do not expect a peer to send us a prefix with one of these ASNs in the path).
Filtering of the Route Servers (ingress to a peer)
The BGP route servers do not add their own ASN in the advertised path, so if you're planning on constructing a filter list to filter the BGP Route servers, do not use the BGP route servers ASN in the path!
We publish IRR record to show networks that peer with the BGP-RS service. Peers are are so inclined, may use this to create their own filters that they can then elect to use to filter the BGP-RS in question. These are available separately for each INX as AS-SETs for:
- CINX: AFRINIC::AS-CINX-RS
- DINX: AFRINIC::AS-DINX-RS
- JINX: AFRINIC::AS-JINX-RS
- NMBINX: AFRINIC::AS-NMBINX-RS
This is also published at PeeringDB