-
- Downloads
Add role for wireguard
Setup wireguard interfaces, configure and deploy keys. Private keys are stored in a file on the host. Public keys are stored in facts, enable fact-caching to allow running the role on a subset of the peers. The dictionary key (interface name) must be the same on all hosts (it identifies the network). At least one peer needs to have a static port specified, so other peers can connect to it. Peers are specified using an inventory hostpattern. This doesn't setup any packet forwarding, DNS server or other VPN features. It just enabled p2p connections (to potentially multiple peers), e.g. to allow serving usually unencrypted applications (like NFS) over an encrypted connection.
Showing
- wireguard/defaults/main.yml 8 additions, 0 deletionswireguard/defaults/main.yml
- wireguard/handlers/main.yml 7 additions, 0 deletionswireguard/handlers/main.yml
- wireguard/tasks/install-Archlinux.yml 6 additions, 0 deletionswireguard/tasks/install-Archlinux.yml
- wireguard/tasks/install-Debian.yml 6 additions, 0 deletionswireguard/tasks/install-Debian.yml
- wireguard/tasks/main.yml 43 additions, 0 deletionswireguard/tasks/main.yml
- wireguard/templates/wireguard.conf.j2 15 additions, 0 deletionswireguard/templates/wireguard.conf.j2
Loading
Please register or sign in to comment