Route Servers

SFMIX route servers enable multilateral peering through a single BGP session (ideally two for redundancy). The route server aggregates and redistributes participant routes, so you can start peering immediately without negotiating bilateral sessions.

Direct peering is still encouraged; route server use is optional. Configuration is generated with arouteserver.

For resilience, SFMIX runs two distinct stacks:

• BIRD on Linux, with Routinator for RPKI
• OpenBGPD on OpenBSD, with rpki-client for RPKI

Configuration summaries: BIRD/Linux · OpenBGPD/OpenBSD

Use the Route Browser (Alice LG) to debug route filtering. SFMIX implements Euro-IX standardized Large BGP Communities where possible.

Routing Security

Route servers filter announcements based on RPKI, IRR, and max-prefix limits (from PeeringDB). RPKI Invalid routes are rejected; RPKI Unknown routes are currently allowed.

SFMIX publishes the IRR as-set “AS-SFMIX-RS” via ARIN to help participants build IRR-based filters.

Connection Information

BGP Communities for Propagation Control

Control how your prefixes are propagated to other participants:

BGP Communities for Informational Metadata

Metadata communities indicate where routes were learned and participant attributes. See Locations for site codes.

BGP Communities to Explain Filtration

Filtered routes are not discarded — they are tagged internally and excluded from redistribution. This allows operators to use the Route Browser to diagnose why routes are filtered or accepted.