Connecting to the exchange

Steps for Connecting

  • Acknowledge all logistical and technical requirements below.
  • WVIX only supports single-mode fiber connections. 
  • Fill out the Connection application
  • Upon connection, WVIX will issue a v4 & v6 allocation. New participants may be placed in a quarantined network segment for initial turn-up or debugging.
  • Configure required sessions and optional route server sessions.
  • Pay any applicable cross connect fees and your yearly port fee.

Logistical Requirements

  • Participants are required to have at least one representative subscribed to the members mailing list.
  • Correspondence or discussions on the mailing lists are considered confidential to participants, members, and sponsors.
  • WVIX is a non-profit, all volunteer run organization. No SLA is provided. 
  • Participants may not sniff traffic between other participants.
  • The WVIX peering fabric is built on significant donated connectivity, physical space, power, and additional infrastructure, with the express intention of operating as a peering fabric and not a transport or carrier replacement. If you are use the fabric for  these purposes you will be asked to stop and failure to stop will result in your port being terminated and future connectivity will be scrutinized. 

Technical Requirements

  • Participants must utilize an ASN (autonomous system number) that is allocated by an RIR (regional internet registry), such as ARIN. Private or reserve ASN’s are not acceptable – as specified by RFC 1930 or RFC 6996.
  • A single source MAC address is allowed per a participant physical port or logical link aggregation grouping. Additional sourced MAC addresses are forbidden.
  • No broadcast traffic (such as CDP, LLDP, DHCP, STP) is allowed over the fabric, except IPv4 ARP neighbor discovery.
  • An MTU of 9000 is supported
  • All participants are required to setup a BGP session with the WVIX looking glass server. This service is utilized purely for debugging purposes; no traffic is exchanged over this peering session.
  • Participants must not allow WVIX subnets to propagate externally from their network and should minimize internal propagation as much as able. If a participant’s network beyond their WVIX edge router(s) can reach the WVIX subnet addresses ( & 2001:504:139::/48 and, ACLs are requested in order to prevent this.
  • Participants may not point default or otherwise use another participant’s or IX resources.  
  • Participants are encouraged to utilize the WVIX route servers, where appropriate for their organization traffic engineering policies.

Article Details

Article ID: