Tech Notes


  • Addresses are assigned by AIXP as shown on the pages under the “PEERS” tab
  • The IXP IP address blocks are local only and must not be advertised anywhere.


  • Most peering requirements can be accommodated on the layer 2 fabric without resorting to VLANs.
  • However, tagging and private VLANs can be configured where required, but only one MAC address will be accepted per physical port.
  • AIXP will assign VLANs as required for private peering.


  • IPv6 has special requirements:
    • IPv6 interfaces must disable auto config (Cisco “ipv6 nd prefix default no-autoconfig no-rtr-address”)
    • IPv6 interfaces must disable router advertisements (Cisco “ipv6 nd suppress-ra”) and should disable receiving them (Linux “echo 0 > /proc/sys/net/ipv6/conf/eth<N>/accept_ra”)


  • Participants are strongly encouraged to establish BGP peering with the route servers in order to gain maximum benefit. Route distribution can be controlled with communities (see below).
  • BGP sessions should be established with the appropriate ASN (e,g, HFXIX ASN 13770).
  • There are two route servers at each IXP for redundancy. At HFXIX for example, those route servers are and for IPv4, and 2001:504:37:10::20 and 2001:504:37:10::30 for IPv6. BGP sessions should be established with both for consistency and reliability.
  • BGP exports are unchanged from the import. Communities, AS paths, etc. are exported as they were imported. This means that the IXP ASN will not show up in exports, and modern routing engines will object to the BGP peer AS being absent. To avoid this check in Cisco IOS, add the statement “no bgp enforce-first-as” to the BGP configuration. Other servers (Quagga, JunOS, etc) have similar statements.
  • Communities can be used to control how your routes are advertised. Route Server communities are applied in the table order. Note: it is important that extended communities only be used for 32 bit ASNs. For example, the community [0,13770] must not be an extended community; the route-servers require extended communities of type “origin” such that an example for a 32-bit ASN is [origin:64600:4200000000] reference: RFC 4360 – Section 5
    Communities examples (using HFXIX ASN 13770 as an example) 
    0:peer-as -OR- 64600:peer-asPrevent announcement of prefix to AS peer-as
    13770:peer-asAnnounce prefix to AS peer-as
    0:13770 -OR- 64600:13770Prevent announcement of prefix to all participants
    13770:13770Announce prefix to all participants (default action)