I noticed earlier that LONAP had passed a fantastic milestone just before the weekend – of the ninety nine networks which are plugged into the exchange, more than half of the networks choose to connect to each other via the route-server.
A route-server is a fantastic way for networks to start to peer (swap internet traffic) at Internet Exchanges, and results in instant success after connection.
A network with an open peering policy can connect to the internet exchange, and then get peering with more than half of all the other networks on the exchange by bringing up a single pair of BGP sessions. When a route-server peering is established, a BGP session is setup between your router and LONAP’s route database. LONAP advertise all of the prefixes of the other connected members to you, but the traffic between you and the other members flows between you and your peer directly (it does not need to traverse the route-server.)
Members do not need to open their network to their own customers at the route servers, they can send special messages to the route-servers to prevent certain networks from seeing prefixes.
Route-servers are not new, but have had a bad reputation for stability for several years. With our colleagues at several other community exchanges, including the LINX, we shared bugs, workarounds, and feature requirements with each other and the main open-source route-server vendors. Eventually, we were able to report considerable improvement in stability last December.
As a result, we at LONAP selected BIRD and OpenBGPd as our route server vendors, and built a support framework to link our configuration with the LONAP configuration system. Since then we have been advocating the route-servers to our members, and the fact that they are now providing a stable stepping-stone to more than half of our peers shows that this effort was worthwhile.
If you would like to start to peer, but need to be assured of instant success and results, then contact LONAP for information about how the route-servers at LONAP can help.