Route Servers – AS214591

frankonIX operates three route servers. They are equivalent, independent of each other and located in different facilities. Please peer with all three – three sessions per address family is the normal state. That is what keeps your connectivity up while we do maintenance.

Route server ASN Location IPv4 IPv6
RouteServer01 214591 NorthC Nuremberg 193.34.203.193 2001:7f8:15b:1::c122:cbc1
RouteServer02 214591 nLighten Nuremberg 193.34.203.194 2001:7f8:15b:1::c122:cbc2
RouteServer03 214591 Hetzner Nuremberg 193.34.203.195 2001:7f8:15b:1::c122:cbc3
Peering LAN IPv4 193.34.203.192/26
Peering LAN IPv6 2001:7f8:15b:1::/64
VLAN 600
MTU 1500

Ready-to-use configuration snippets for Junos, Arista, Cisco, BIRD, FRR, VyOS and OpenBGPD are on the Configuration Examples page.


RPKI validators

We run two Routinator instances and make them available to our members on the peering LAN as an additional service. Using them is entirely optional – if you already run your own validators, please stay with them. If you would rather not maintain your own, you are welcome to use ours.

Validator IPv4 IPv6 Port
rpki01 193.34.203.196 2001:7f8:15b:1::c122:cbc4 3323
rpki02 193.34.203.197 2001:7f8:15b:1::c122:cbc5 3323
Most common mistake: the RTR port is 3323, not the default 323. Almost every implementation defaults to 323, so the port has to be stated explicitly.

Configure both validators, not just one. A single RTR session covers both address families: the transport is independent of what gets validated – a session over IPv4 delivers ROAs for IPv4 and IPv6.

Origin validation is active on the route servers themselves. Announcements evaluated as RPKI invalid are not passed on.


What gets filtered

Your announcements are dropped if any of the following applies:

Check Limit
Prefix length IPv4longer than /24
Prefix length IPv6longer than /48
Bogons / martiansRFC-reserved networks
AS pathempty or longer than 64 entries
First AS in the pathmust be your ASN
Next hopmust be your own peering IP
Transit networks in the pathknown transit ASNs
IRRDBprefix or origin AS not in your AS-SET
RPKIorigin validation = invalid

We use IRRDB filtering. Please keep the AS-SET in your profile up to date – without one we filter on your ASN alone, and anything coming via your downstreams is dropped. Filter data is regenerated every six hours.

RFC 8326 graceful shutdown is supported: announcements carrying community 65535:0 get local_pref = 0, so you can signal maintenance without tearing the session down.


BGP communities

frankonIX uses a 32-bit ASN. Classic RFC 1997 communities (214591:x) therefore do not work. Only large communities per RFC 8092 are supported.
What you can send
Large community Effect
214591:0:<peer-as>Do not announce to this peer
214591:1:<peer-as>Announce to this peer
214591:0:0Announce to nobody
214591:1:0Announce to everyone (default)
214591:101:<peer-as>Prepend once towards this peer
214591:102:<peer-as>Prepend twice
214591:103:<peer-as>Prepend three times
214591:101:0103:0Prepend towards all peers

Example – announce to everyone except AS64496: 214591:1:0 plus 214591:0:64496

What we set
Large community Meaning
214591:1000:1RPKI valid
214591:1000:2RPKI unknown
214591:1000:3RPKI not checked
214591:1001:1IRRDB valid
214591:1001:2IRRDB not checked
Filtering reasons

Dropped routes never reach the other members, but they are visible in the looking glass together with the reason:

Large community Reason
214591:1101:1Prefix too long
214591:1101:2Prefix too short
214591:1101:3Bogon
214591:1101:4Bogon ASN
214591:1101:5AS path too long
214591:1101:6AS path too short
214591:1101:7First AS ≠ peer AS
214591:1101:8Next hop ≠ peer IP
214591:1101:9Prefix not in IRRDB
214591:1101:10Origin AS not in IRRDB
214591:1101:11Prefix not in origin AS
214591:1101:12RPKI unknown
214591:1101:13RPKI invalid
214591:1101:14Transit-free ASN in the path
214591:1101:15Too many communities

Questions? Support & Contact