Sunil Mohan Adapa 6e1b0a3642

wireguard: Handle client connections through network manager ...

- Any changes done directly using 'wg' command need to be redone after a reboot
  and disable/enable sequence. Let that duty be handled by network manager.

- Handle (none) values for keys and 0 values for latest handshake from 'wg'
  dump command output.

- Don't store public/private keys for wireguard in /var/lib. Let Network Manager
  deal with the storage of secrets.

- Create client connections in the 'external' zone.

- Show allowed IPs for each client in the main page.

- Show server connection public key only for clients. We use different key pairs
  when connecting to each of the servers.

- Separate out configuration information and status information in the show
  page.

- Allocate IP addresses to each of the clients.

Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>

2020-01-18 13:53:35 -05:00

..

data

wireguard: Add skeleton for new app

2020-01-18 13:52:35 -05:00

templates

wireguard: Handle client connections through network manager

2020-01-18 13:53:35 -05:00

__init__.py

wireguard: Handle client connections through network manager

2020-01-18 13:53:35 -05:00

forms.py

wireguard: Handle client connections through network manager

2020-01-18 13:53:35 -05:00

manifest.py

wireguard: Implement adding client

2020-01-18 13:52:38 -05:00

urls.py

wireguard: Only use network manager for connections to servers

2020-01-18 13:53:31 -05:00

utils.py

wireguard: Handle client connections through network manager

2020-01-18 13:53:35 -05:00

views.py

wireguard: Handle client connections through network manager

2020-01-18 13:53:35 -05:00