01 / 04 · Technical Documentation

Route servers and connection details

Route server ASN, peering LAN, addresses of the three route servers and what members need to know when setting up sessions.

Connection details#

Route server ASN
214591
Peering LAN IPv4
193.34.203.192/26
Peering LAN IPv6
2001:7f8:15b:1::/64
MTU
1500
Handover
untagged, autonegotiation off

Route servers#

Three equivalent, mutually independent route server pairs. Members should configure all three, i.e. three sessions per address family.

Route serverIPv4IPv6
RS01193.34.203.1932001:7f8:15b:1::c122:cbc1
RS02193.34.203.1942001:7f8:15b:1::c122:cbc2
RS03193.34.203.1952001:7f8:15b:1::c122:cbc3

What members need to know#

  • The route servers are transparent: AS214591 does not appear in the AS path, and the next hop remains that of the announcing member. On many platforms enforce-first-as therefore has to be disabled for these sessions.
  • No MD5 passwords, no multihop; sessions are actively established from both sides.
  • Prefix limit: the route server accepts only as many prefixes from each member as stated in PeeringDB; without an entry, 250 (IPv4) and 50 (IPv6) apply. If the limit is exceeded, the session is restarted. Keep PeeringDB up to date.
  • Software: BIRD 2, configuration generated by IXP Manager.

Example configurations#

Detailed example configurations are available in the portal: manager.frankonix.net/public-content/routeserver

Looking glass: manager.frankonix.net/lg Technical questions: support@frankonix.net Last updated: November 2026