Technical information

Membership rules

Eligibility

• All members must have a valid, public (non-private) ASN and use BGP-4 for peering.
• Every member arranges its own peering agreements with other members. FIXO does not arrange peering agreements.

Acceptable use

• Only settlement-free peering traffic may be exchanged over FIXO. Members must not sell transit over the FIXO infrastructure, or act as a transit ASN for traffic exchanged on FIXO.
• The FIXO infrastructure may only be used for peering with other FIXO members.
• The IPv4 address space assigned to FIXO must not be announced to other networks.
• Interfaces connected to FIXO must only use the addresses FIXO has assigned to them.

Operations & support

• FIXO does not run its own 24/7 NOC, but is covered by the 24/7 on-call staff at Blix Solutions AS. Because of this, work done outside normal working hours (09:00–16:00 CET/CEST) is charged.
• FIXO treats traffic data as private. Members can only see graphs for the ports they use.
• Basic services do not include colocation, but FIXO can provide pricing for it.
• FIXO cannot be held responsible for any direct or indirect loss caused by an outage.
• FIXO can and will disconnect or suspend any member that breaks these terms or causes operational problems for the exchange.

Port requirements

• Spanning tree, CDP, IPv6 router advertisements (RA), IPX and similar protocols must be turned off on interfaces connected to FIXO.
• Frames forwarded to FIXO must use one of these ethertypes: 0x0800 (IPv4), 0x86DD (IPv6) or 0x0806 (ARP).
• All frames forwarded to FIXO must have the same source MAC address.
• Frames must be addressed to a unicast destination MAC address, except for broadcast ARP and ICMPv6 neighbour discovery.
• Proxy ARP is not allowed.
• No link-local traffic is allowed on FIXO.
• IP packets addressed to the FIXO IPv4 peering prefix must not automatically be forwarded onto FIXO.

Peering LAN

Your port gets one IPv4 and one IPv6 address from these prefixes, assigned by FIXO.

Route servers

FIXO runs two route servers, each with IPv4 and IPv6 sessions, under AS61300. Instead of setting up a bilateral session with every other member, you can peer with the route servers and receive routes from everyone else who does the same. You control where your routes go with simple BGP communities (see below).

BGP communities

Tag your announcements to the route servers with these communities to control which peers receive them.

IRR filtering

The route servers do strict IRR filtering. FIXO maintains the AS-FIXO as-set in the RIPE database. Make sure your route objects and as-set are up to date before you announce new prefixes.

Example configurations

Ready-made route-server configurations you can adapt: