# MeshVPN Meeting 2021-03-22

Today's meeting is about running multiple Wireguard interfaces on one Linux machine for testing purposes.

## Setup

You'll need a Linux environment. If you're on Windows, use Virtualbox with Ubuntu or something.

Install `iperf3`, `go`, `make`, `wireguard-tools` and `git` in your Linux environment.

Clone this repo from git: https://github.com/malcolmseyd/wireguard-go

Build `wireguard-go` like so:

$ make
go build -v -o "wireguard-go"
... other stuff ...

There should be a file in the directory named `wireguard-go`. If so, you should be ready to go!

## Testing

Head to ./tests and run netns as follows:

$ cd tests/
$ sudo ./netns.sh ../wireguard-go 
... testing stuff ...

The end of the tests should look like this:


This test suite just tests whether you can get a basic test with multiple Wireguard interfaces running. Later, I'll actually plug in our software or something. I'll also package this up so you Windows users can stay in the terminal.

## Issues

The test was really jank on my machine and failed randomly every now and then. If it fails, try again a few times to make sure it wasn't a fluke.

### Common Errors

These happen during the setup phase sometimes.



I have no idea what causes them :shrug:

## What even is this?

It's a script that sets up some Wireguard interfaces in different network namespaces and sees if they can transfer data. As you might have noticed, I forked this from the official Wireguard Go project and modified the test. Here's what the comment at the top says.

 This script tests the below topology:

 ┌─────────────────────┐   ┌──────────────────────────────────┐   ┌─────────────────────┐
 │   $ns1 namespace    │   │          $ns0 namespace          │   │   $ns2 namespace    │
 │                     │   │                                  │   │                     │
 │┌────────┐           │   │            ┌────────┐            │   │           ┌────────┐│
 ││  wg1   │───────────┼───┼────────────│   lo   │────────────┼───┼───────────│  wg2   ││
 │├────────┴──────────┐│   │    ┌───────┴────────┴────────┐   │   │┌──────────┴────────┤│
 ││192.168.241.1/24   ││   │    │(ns1)         (ns2)      │   │   ││192.168.241.2/24   ││
 ││fd00::1/24         ││   │    │127.0.0.1:1   127.0.0.1:2│   │   ││fd00::2/24         ││
 │└───────────────────┘│   │    │[::]:1        [::]:2     │   │   │└───────────────────┘│
 └─────────────────────┘   │    └─────────────────────────┘   │   └─────────────────────┘
                           └──────────────────────────────────┘

 After the topology is prepared we run a series of TCP/UDP iperf3 tests between the
 wireguard peers in $ns1 and $ns2. Note that $ns0 is the endpoint for the wg1
 interfaces in $ns1 and $ns2. See https://www.wireguard.com/netns/ for further
 details on how this is accomplished

We'll also be able to test NATs with this as well, which is pretty exciting.

## Tasks

* Get this test to run successfully on your machine.
* Make a Vagrantfile for this
* Plug `meshvpn` into the test somehow