Feature request: Wireguard configuration files reading for VPNSP=custom

[qdm12]

⚠️ Blocked by #611

What's the feature? 🧐

• Parse each configuration and extract:
  • Endpoint IP
  • Endpoint port
  • Allowed Addresses
  • Private key
  • Public key
  • Pre-shared key
  • Checks to ensure this is a client configuration, not a server one.
• Read all configuration files from /gluetun/wireguard/configurations
  • List all possible servers from in memory
  • Hot reload / periodic reload / reload on request of the files

[qdm12]

From @ksurl:

You can set to wg.conf as a default but configurable via an environment variable?

From @JBtje

wg.conf sounds good, configurable via env even better

My take on it:

Let's keep it as constant /gluetun/wireguard/wg.conf, not configurable:

• so there is less chance of user error; one can always bind mount from a different file name.
• Gluetun will support multiple openvpn/wireguard config files read from a directory, so the file name won't matter anymore.

Although I'm opened to another name than wg.conf as well.

[qdm12]

This is more or less done. Wireguard configuration files can be read:

• from /run/secrets/wg0.conf (6096b7a)
• from /gluetun/wireguard/wg.conf (feat(settings): support Wireguard ini config files #1120)

It doesn't read all the configuration files from /gluetun/wireguard/configurations or hot reload them, but I don't think that's really necessary/useful for now. Another issue can be created if there is a need for it.

[github-actions]

Closed issues are NOT monitored, so commenting here is likely to be not seen.
If you think this is still unresolved and have more information to bring, please create another issue.

This is an automated comment setup because @qdm12 is the sole maintainer of this project
which became too popular to monitor issues closed.