{"id":8042,"date":"2025-01-15T15:17:17","date_gmt":"2025-01-15T14:17:17","guid":{"rendered":"https:\/\/mix2024.it-mix.net\/route-server\/"},"modified":"2025-09-04T12:07:20","modified_gmt":"2025-09-04T10:07:20","slug":"route-server","status":"publish","type":"page","link":"https:\/\/www.mix-it.net\/en\/route-server\/","title":{"rendered":"Route Server"},"content":{"rendered":"
\n\n
<\/div>\n\n\n\n

To simplify the management of peering agreements and facilitate the onboarding of new participants, MIX provides a route server service on its peering LANs.<\/p>\n\n\n\n

This mechanism allows participants to configure and manage multiple BGP sessions with other peers using a single BGP session.<\/p>\n\n\n\n

This approach does not replace traditional bilateral peering agreements but rather serves as a natural complement to them.<\/p>\n\n\n\n

<\/div>\n\n\n\n
Technical Features<\/strong><\/h5>\n\n\n\n

Each participant connected to the route server platform is associated with a list of prefixes considered valid for BGP announcements. This list is generated by querying major IRRDB databases, using the participant\u2019s Autonomous System (AS) number or, if necessary, a specific AS-set provided by the participant. <\/p>\n\n\n\n

<\/div>\n\n\n\n
Prefix Validity Requirements<\/strong><\/h5>\n\n\n\n

It is essential for each participant to keep their information updated in the IRRDB databases. Specifically, for each prefix announced on MIX, there must be a corresponding route<\/strong> (or route6<\/strong>) object with the participant\u2019s AS number as the origin<\/strong>. Only prefixes meeting this condition will be included in the valid prefix list. <\/p>\n\n\n\n

<\/div>\n\n\n\n
BGP Session Management<\/strong><\/h5>\n\n\n\n

Once the BGP session is established, IP traffic will be exchanged directly between peering LAN neighbors.<\/p>\n\n\n\n