Known Issues

Terraform doesn't always add or remove entries in the routing table because of a race condition. See issue #5

Look in ~/proxycannon-ng/nodes/aws/.routecmd. It should match the same IP entries that terraform just launched (or deleted).

You can check the current routing table on your control-server with ip route show table loadb

The Fix:

Manually add or remove IPs in .routecmd file until it matches current state. If you ran a terraform destroy and there are still routes in .routecmd you are ok to just delete the whole file, it will be readded on the next terraform run.

---

Connectivity issues due to installation commands that do not persist a reboot

If the control server is rebooted after running install.sh network connectivity will be broken.

The Fix:

See #21 for a detailed fix.