A route server is a network device that simplifies the exchange of routing information at Internet Exchange Points (IXPs). Instead of each network creating multiple individual peering sessions, a route server allows networks to share their routes through a single connection.
At LINX, route servers allow members to connect with hundreds of networks and play a critical role in secure and efficient traffic optimisation.
What is a Route Server?
A route server is a central network device at an IXP that receives and distributes routing information between connected networks. Networks announce their IP prefixes to the route server using forms of routing protocol, such as Border Gateway Protocol (BGP), and the route server then shares these routes with other networks that opt to receive them.
The Importance and Benefits of Route Servers
Without route servers, each network would need to establish bilateral (individual) peering sessions with each network they wish to connect with, which could mean additional administrative burden or challenges in scaling.
Route servers help networks:
- Simplify peering operations: Networks connect via a single session rather than multiple individual sessions.
- Scale efficiently: As your peering needs grow, route serves let you connect to more networks without adding more BGP sessions.
- Improve resilience and reliability: Centralised route distribution reduces configuration errors, helping to maintain redundant, stable and consistent traffic exchange.
- Optimise network performance: Route servers help networks select the best paths for traffic, reducing latency and improving end user experience.
Overall, route servers make peering simpler, scalable and resilient whilst improving overall network performance.
How LINX Uses Route Servers
Route servers are part of the core infrastructure here at LINX and run across all Peering LANs, helping member exchange routing information efficiently and reliably.
By connecting to a route server, networks can exchange routing information efficiently, simplify operations, and scale their peering without multiple individual BGP sessions.
The LINX route servers support members by:
- Distributing routes centrally: Members announce their prefixes, and the route servers share them with all networks that’ve opted to receive them.
- Allowing flexible routing polices: Members can control which routes they advertise and accept, giving them greater control over their connections.
- Enabling scalable peering: A single BGP session lets members connect with multiple networks, reducing overheads, whilst expanding connection opportunities.
Frequently Asked Questions
What does a route server do?
A route server redistributes routing information between networks at an Internet Exchange, allowing networks to exchange traffic without establishing direct bilateral peering sessions with every other participant.
Do I need a route server to peer?
No, peering can be done bilaterally, but route servers make connecting to multiple networks easier, faster, and more efficient.
Does using a route server add latency to my traffic?
No. Because the route server is only involved in the control plane (routing updates) and not the data plane (actual traffic), it has zero impact on your latency or throughput.
What’s the difference between a route server and a router?
A route server exchanges BGP routing information but doesn’t forward data packets. Routers both exchange routes and forward traffic. Route servers operate only on the control plane, while data flows directly between peering networks.
Does traffic pass through the route server?
No. Route servers only exchange routing information. All data traffic flows directly between peering networks, ensuring optimal performance and low latency.
Can I control which routes I receive from a route server?
Yes. LINX route servers support comprehensive BGP communities that allow members to implement selective peering, filter specific routes, and apply custom routing policies.
< Go Back