EVIX

Get connected

Anyone with an ASN is welcome, and it costs nothing. Read the four points below first, then send the form. It saves everyone a round of emails.

Before you apply

1 You need your own ASN

EVIX is a real internet exchange, so you must have a non-reserved ASN assigned to you by an RIR. If you do not have one yet, experiment with DN42 first and come back once you are sure you want to register an ASN.

2 IPv6 by default, IPv4 only if you need it

Our IPv4 range is nearly full, so please request IPv4 only if you are actually going to announce IPv4 space. We check before allocating. An IPv6-only connection is completely normal here, and you can always ask for an IPv4 address later. If your situation is unusual, say so in the comments and we will work it out.

3 Pick the right connection type

This is the single most common mistake, so it is worth a careful read.

  • Connecting from a VM at one of our hosting partners (Free Range Cloud, iFog, Xenyth) or from a port in a facility we are in? Choose Local/VPS/Other. Not a tunnel.
  • Frankfurt and Vancouver are local-only. They have no tunnel endpoint at all. The form will force the local type when you pick them.
  • Connecting from your own hardware elsewhere? Choose a tunnel type. VXLAN is our recommendation unless you have a reason to prefer another.

iFog customers, one specific thing. Ask iFog to add a dedicated EVIX interface to your VM, and configure your EVIX addresses on that new interface. Do not put EVIX on your existing FogIXP interface: FogIXP is iFog's own exchange on a different VLAN, and your frames will never reach us. This trips up almost everyone who connects from iFog.

4 Know what happens next

We are volunteers, so there may be a wait, particularly during the school year. Your request becomes a ticket and we do get to all of them, so you are not forgotten. Rejections are rare and we always explain them.

Please allow mail from helpdesk@ev-ix.org through your filters: your setup instructions and any later notices about your session come from there, and we have landed on blacklists before now.

When you do hit a problem, check the example configuration and the troubleshooting checklist first. Then email us with your configuration, logs, and the output of a ping and traceroute to the route server. Please be kind: we are volunteers with our own lives, and harassment will get you removed from the exchange.