Route server

All participants are welcome to establish a peering to the STIX Route Servers and exchange prefixes this way.

The route servers should not be seen as a replacement to bilateral peerings between the participants and is provided by STIX on a best effort basis without any guarantee on availability.

Technical info

ASN: 43286
RS1: 185.1.124.251 / 2001:7f8:cf::fb
RS2: 185.1.124.252 / 2001:7f8:cf::fc

Sanity checks

• Routes with Prefix lengths longer than /24 for IPv4 and /48 for IPv6 will be rejected
• Routes must be in the list of the main IRRDB databases for the ASN or the AS-SETs of the participant
• The first ASN in the as-path must be the one of the peering ASN
• Routes that are well-known bogons or martians will be rejected
• Routes with one or more “transit free” ASNs in their as-path will be rejected
• RPKI route origin validation is active. Prefixes marked as INVALID will be rejected

BGP Configuration Notes

Once the BGP session is established, IP traffic is exchanged directly between peers on the peering LAN.

• The route server’s IP address is not used as the next-hop.
• The route server’s AS number does not appear in the as-path.
• “no bgp enforce-first-as” must be enabled so that routes are accepted.

BGP Communities

The route servers provide well known communities to allow to control the distribution of the prefixes.

Standard Communities

Default behavior is announce to all peers.

Large Communities (Recommended)

Use large communities if supported, especially for 32-bit ASNs.

You should not mix standard 16-bit communities and large communities – please choose one or the other.

AS Path Prepending (Large Communities only)

RFC1997 Communities

Well-known communities such as NO_EXPORT and NO_ADVERTISE are passed through unchanged by the route servers.