LOCIX Route Servers

At LOCIX we maintain some route servers
If you want to peer with them , you can found their configuration below
We also operate an AS112 instance. You can peer with them too. More details there

We highly recomend you to peer with all our routeservers

Nb: all our servers use IRRDB filtering, be sure you define your AS-SET on your ixp manager profile
and have route objects on your RIR database

Route server configuration

Hostname	ASN	IPv4	IPv6
rs01.locix.online	202409	185.1.166.100	2001:7f8:f2:e1::babe:1
rs02.locix.online	202409	185.1.166.200	2001:7f8:f2:e1::dead:1
rs03.locix.online	202409	185.1.166.254	2001:7f8:f2:e1::be5a

Route server action codes / Bgp communities

We support some basic bgp large communities to let you do specific anouncements

Nullrouting

At LocIX, we maintain nullroute community.

Community: (202409, 666, 666)

To be fully compatible, you need to follow those rules:
- Accept up to /32 or /128 with our nullroute community
- Send us your blackhole route with this community
- Have this route included into your subnet (irrdb filtered)
- Blackhole on your side any route received with that community

Announce / don't announce to specific members

By default, you got reanounced to every members.
If you don't want that, you can combine community below to do more specific things

Announce nowhere	(202409, 0, 0)
Announce to everyone	(202409, 1, 0)
Announce to specific member	(202409, 1, <peerasn>)
Don't announce to specific member	(202409, 0, <peerasn>)

Example

For announce to no one except HE, you define the two community below:
(202409, 0, 0) and (202409, 1, 6939)

You want announce to everyone except AS206499:
(202409, 0, 206499)

Prepend route to specific AS

With route server, you can prepend up to 3 time announcement for specific member
This setup can be usefull if you want to preference other sessions with that member

To do that, just add the community below
(202409, 101, <dstasn>)

The third digit define the number of prepend. 101 = 1x , 102 = 2x , 103 = 3x