The team is hosting an XMPP+TURN service in the cloud to help new users get started using the software. With this service, we provide prospective new users with configuration files that allow a plug-and-play deployment of Evio nodes using Docker containers for x86/Linux.

To support ramping-up many new users, the trial accounts are limited to five nodes and expire in a 2-week period; these may change depending on user demand.

Step 1: request accounts and configuration file

Click here enter your request; we will review and contact you by email to provide you with configuration files. The information we ask for is:

  • Contact email
  • Project name
  • Brief project summary

Step 2: Deploy nodes

Once you receive the configuration files, the easiest way to get started is to run Evio Docker containers in an x86/Linux computer, using the configuration files you received.

To install Docker:

curl -fsSL | sudo apt-key add -
sudo add-apt-repository "deb [arch=amd64] bionic stable"
sudo apt-get update -y
sudo apt-get install -y openvswitch-switch \
                        python3 python3-pip python3-venv \
                        apt-transport-https \
                        ca-certificates \
                        curl git \
                        software-properties-common \
                        docker-ce-cli \
sudo groupadd -f docker
sudo usermod -a -G docker $USER
sudo docker network create dkrnet

Logout and login so that group changes are in effect.

If you already have Docker installed, you just need to create a Docker network, and use the -v Docker option to mount the configuration file and log directory.

You can start the container and bind to the dkrnet network as follows. Alternatively, you can replace dkrnet with host below to use Docker’s host networking - if you only run a single container in your host.

docker run -d -v /path_to/config-001.json:/etc/opt/edge-vpnio/config.json -v /path_to/logs/001:/var/log/edge-vpnio/ --rm --privileged --name evio001 --network dkrnet edgevpnio/evio-node:20.7 /sbin/init

Step 3: Test it out

By default, the files configure node addresses in the subnet, and - range. A simple ping test:

docker exec -it evio001 /bin/bash
# ping