Test bug #33: make sure exitnode/create_exitnode.sh still works

[gobengo]

Bennie mentioned this as a testing task for bug #33 in 8/7/2018 Software WG

[bennlich]

Right now, this would consist of:

1. Spin up an ubuntu machine w/ a public ip (e.g. on digital ocean)
2. Run the create_exitnode.sh script to deploy a fresh exitnode to this machine (be sure to use the branch with the fix: support for babeld 1.8.2 #15)
3. Modify tunneldigger.conf on a flashed home node to point to the new exitnode
4. See if you can load a webpage on the big internet from the home node's public SSID
5. See if you can run the new babeld-info script to check babeld's status (should be in the PATH). The home node should show up in the list of routes.

Going to mark this as a good first issue because it touches a lot of pieces of the system. Will probably be hard for a new person to tackle this alone, but it would be a good first issue to pair on.