Technical

Technical Guidelines

These guidelines are important. Everyone following the same rules will ensure that the Internet Exchange is reliable and safe.

Continue Reading

Technical Guidelines

NAPAfrica rules restrict the type of traffic and number of source MAC addresses that any member is allowed to send to the exchange. The following guideline provides information on how to configure your interface towards NAPAfrica to only send allowed traffic to the exchange.

  • Connected ports must be Ethernet. 100Mbit ports should be configured with a fixed 100Mbit speed, and Full Duplex. Gigabit Ethernet ports can be configured as auto-sensing or manual. Please tell is what you prefer.
  • Any intermediate devices between the NAPAfrica switch and your router, for example an aggregation switch, a third-party Ethernet transport provider, or media conversion devices must not emit any traffic towards the exchange.
  • By default, participants will be assigned an access port on the public peering VLAN. Multiple VLAN ports are available, and we will use 802.1q VLAN tags (Ethertype 0x8100) to signal which VLAN the frame is in. You should not send frames with VLANs that are tagged for VLANs which we have not configured on your port. A change of service from a single VLAN port to a port supporting 802.1q tagging will cause a small interruption to your service.
  • We recommend that interfaces on an access port have 1500 byte MTUs. Ports with 802.1q VLAN tagging can be 1516 so that the containing frame does not need to be fragmented.
  • All frames from a single port, which are forwarded to the NAPAfrica exchange must have the same source MAC-address. If this is not configured, then port-security on the NAPAfrica switch will shut down your peering port. This technique is the most important loop prevention technology used on NAPAfrica, so exceptions are not permitted.
  • On the public peering LAN, only Ethertypes 0x0800 (IPv4), 0x08dd (IPv6) and 0x0806 (ARP) are permitted. If you wish to exchange other types of packets with connected participants, then a Closed User Group VLAN can be created between the participants who wish to exchange other types of traffic.
  • Connected networks should disable Proxy ARP on the router interface connected to NAPAfrica.
  • Connected networks should disable non permitted link-local protocols on the router interface connected to NAPAfrica. Illegal protocols include DHCP, Spanning Tree, DEC MOP, CDP, VTP and Layer 2 Keepalive packets. The only permitted link-local protocols are ARP and IPv6 Neighbour Discovery.
  • Connected networks must only use BGP to exchange routing information. This explicitly means that other routing protocols such as OSPF, ISIS, EIGRP, and IPv6 Router Solicitation should never be used. It is always forbidden to point any static routes at other exchange participants.
  • NAPAfrica recommend against overloading your ports, and we will get in touch when traffic at 95th percentile exceeds 75% of the port capacity. When traffic reaches 50% of your port capacity, NAPAfrica will discuss suitable upgrade options (higher port capacity or aggregated links)
  • Networks using aggregated ports will follow 802.3ad specifications. The aggregated links must be of the same media type and link speed.
  • All connected networks must BGP peer with the Internet Exchange’s collector. This session allows NAPAfrica to check the health of the Internet Exchange.
  • Connected networks should not export the NAPAfrica peering LAN address space to other networks without permission.

NAPAfrica is always able to help with your peering port configurations.

If we notice that any forbidden traffic is reaching the exchange from your router, we will always contact you with advice in the first instance. However, if we see traffic from you that could damage the stability of the exchange, then we may be required to move your port from the peering LAN into the quarantine LAN while we diagnose the issue with you.