Route Servers

SFMIX route servers let you do 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. Say less, you’re in.

Direct peering is still encouraged; route server use is optional. Config 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

Config 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 get rejected (L); 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 get 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 don’t get discarded — they’re tagged internally and excluded from redistribution. This lets operators use the Route Browser to diagnose why routes got filtered or accepted. Receipts included.