elghazal-a/autowire

Automatically configure Wireguard interfaces in distributed system. It supports Consul as backend.

autowire's Issues

Rebind Consul to wireguard interface

First off congratulations on execution of a genius idea.
I was looking for a solution to exactly that problem.

One minor feature that I would like to see added would be to no also autoconfigure wireguard via consul but also move all consul instances over to the new wireguard network.

Is this even possible or would this create a chicken-egg problem where one relies on the other?

health check failed when runnnig autowire

error messages

chchang@warp:~$ ./autowire -wg-endpoint-ip 123.123.123.123 -wg-range 192.168.10.0/24 -wg-config-folder /tmp/wireguard -wg-port 12000
2021/08/04 10:34:31 INFO: Connecting to consul 127.0.0.1:8500
2021/08/04 10:34:31 ERROR: health check failed for 127.0.0.1:8500
2021/08/04 10:34:31 FATAL: Get "http://127.0.0.1:8500/v1/health/state/any": dial tcp 127.0.0.1:8500: connect: connection refused

why connect to tcp port 8500 ??

Add SAML support

Using Okta/O365/Google with rotating keys is a lot more secure than sharing static keys.

Thank you!

support etcd backend

is there any plan to support etcd as a backend?

Wireguard PostDown

Autowire doesn't have an option to submit "PostDown" commands.

Server Config

[Interface]
Address = 10.200.200.1/24
ListenPort = 51820
PrivateKey = SERVER_PRIVATE_KEY

PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE