-
Notifications
You must be signed in to change notification settings - Fork 103
Known Issues
ccammilleri edited this page Jan 3, 2019
·
5 revisions
Terraform doesn't always add or remove entries in the routing table because of a race condition. See iisue #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.