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.

Caratteristiche tecniche

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

Sanity check

• 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

Note sulla configurazione BGP

Una volta stabilita la sessione BGP, il traffico IP viene scambiato direttamente tra i peer nella peering LAN.

• L’indirizzo IP del route server non viene utilizzato come next-hop.
• Il numero AS del route server non compare nel as-path
• È necessario abilitare “no bgp enforce-first-as” affinché le rotte vengano accettate

BGP Communities

I route server supportano community standard per controllare la distribuzione dei prefissi.

Standard Communities

Il comportamento predefinito è l’annuncio verso tutti i peer.

Large Communities (Consigliate)

Utilizzare le large communities se supportate, specialmente con ASN a 32 bit.

Non mischiare community standard a 16 bit e large communities: scegliere solo uno dei due metodi.

AS Path Prepending (solo Large Communities)

RFC1997 Communities

Le community standard come NO_EXPORT e NO_ADVERTISE vengono inoltrate dai route server senza modifiche.