Getting Started with Peering

Most organisations joining the peering exchanges will configure multilateral peering via the route servers provided at each exchange. This is not a requirement, but it can make the process easier to start with.

Alternatively, organisations can create bilateral peering sessions with other participants on the peering exchanges at any time.

Exchange Requirements

BGP Capable Router

Your own block of IP addresses, at least /24 IPv4, or /48 IPv6

Your own Autonomous System (AS) number


Each exchange has two route servers which hold details of the routes exchanged via multilateral peering. Participants are free to use these servers and/or make their own bilateral peering arrangements with other participants.

The route servers only implement basic filtering. A list of bogons is copied from and these routes are filtered inbound and outbound. In addition both IPv4 and IPv6 default routes are filtered as well as IPv4 prefixes > /24 and IPv6 prefixes > /48.

There are also filters that limit the number of prefixes that any peer can announce:

  • Default Max IPv4 prefixes: 1000
  • Default Max IPv6 prefixes: 100

Any organisation wishing to announce more than these defaults should contact:

Frames forwarded to exchange ports must have one of the following ethertypes:

  • 0x0800 – IPv4
  • 0x86dd – IPv6
  • 0x0806 – ARP

IP packets addressed to NZIX peering LAN’s directed broadcast address shall not be automatically forwarded to NZIX ports.

IP address space assigned to an NZIX peering LAN shall not be advertised to other networks without explicit permission of Vital.

Frames forwarded to exchange ports shall not be addressed to a multicast or broadcast MAC address, except for broadcast ARP and multicast ICMPv6 Neighbour Discovery packets. This includes:

  • ICMP redirects
  • IEEE 802 Spanning Treet
  • Discovery Protocols
  • Interior routing protocol broadcasts, and others

All frames much have the same source MAC address – only one address per port.