wireguard

OS/Environment

None yet, but I'm working on OS X v10.11.6 'El Capitan' client-side. (See 'The way of deployment (cloud or local)' below for details on considered server infrastructure.)

Ansible version

None yet, as I haven't yet gotten that far into setting up Algo.

Version of components from requirements.txt

Not applicable (see above.)

Summary of the pro

Right now in different places in the SE codebase there are references to /opt and then as well to /usr.

All SE code should reference one place only. Could someone please create a PR that fixes this.

This PR should also take PR #454 into consideration (no conflicts)

On Windows, if the authentication flow isn't completed (failure, closed the browser, etc.) then the client keeps showing 'connecting' but doesn't show a clear action to restart authentication.

Clicking disconnect + connect, or log in as a different user will generate a new authentication link and unblock the user, but that's somewhat difficult to discover.

Options for improvement include adding

I think it would be good to describe/list the capture technologies Wireguard is using for each platform. e.g. Windows it using wintun.net driver, Linux it is using /dev/tun etc.

Likely an advanced topic.

@cure rightfully pointed out that we really need a changelog, 0.12.0 is ramping up to be a large release with many breaking changes and having just the included commits is no longer viable.

In addition, we should have PR and Issue templates to make sure users and contributes have a checklist of what to include.

Changelog

I suggest having a file CHANGELOG.md which has a format like:

Found a strange behavior on netclient and found the following codes in netclient/wireguard/common.go

		if keepAliveString == "0" {
			keepAliveString = "15"
		}

Anyone knows why we are doing this?
IMO, Netclient should not decide what the value is, but follow the instructions from the server (otherwise what is the propose to having a server).

Also I found the keepalive value in

Hi,

Seems like I couldn't use this script to install Wireguard sucessfully on CentOS Stream 8.

I have encountered this error during execution:

Error:
 Problem: cannot install the best candidate for the job
  - nothing provides kernel(__skb_flow_dissect) = 0xd82bed9c needed by kmod-wireguard-3:1.0.20210424
  - nothing provides kernel(flow_keys_basic_dissector) = 0xa7e38f12 needed b

Is your feature request related to a problem? Please describe.
Hello team.
I have a task to deploy a tiny and cute frontend, which will distribute wg configs for users of our organization. I decided to use your package, because it is 100% suitable.
We use dedicated server as a wg endpoint (VyOS cluster on vrrp), so I don't need to create peers from UI. I am populating config.json by ansible

• make select for language and region (based on tmdb regions/languages)
• use slider for max download size

Is your feature request related to a problem? Please describe.
I would like to set a custom and static interface name for the client to use with firewall rules

Describe the solution you'd like
An additional option here:

Would work great in my opinion.

**Describe alterna