From: Christian Schmitt <c.schmitt@envisia.de>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: dynamic peer configuration over socket?
Date: Tue, 16 Mar 2021 21:28:35 +0000 [thread overview]
Message-ID: <4fa1c016-9fcb-b1ab-2df6-be774ac6344d@envisia.de> (raw)
Hello,
currently I'm toying a little bit with wireguard and found the
configuration really really simple.
at the moment I'm using openvpn and want to replace it. with openvpn we
dynamically add peers by using the management api.
we have a watcher program that listens the management sockets and
watches until openvpn sends us something like
(https://openvpn.net/community-resources/management-interface/
--management-client-auth):
> MGMT: connect client:
we than need to respond with either client-kill or client-auth
(asynchronously).
this is extremly helpful because it means we can have a database where
all our peer configuration is held and openvpn asks if the client allowed.
I could not find something like that with wireguard, the only way I
would find, if our service would poll for new configuration and apply it
if wireguard does not know the peer, but this is error prone and does
not work in my ha topology that well. is there something planned to make
that happen? it's btw. also painful to manage such a big config with
hundreds of client peers.
Best Regards
Christian
reply other threads:[~2021-03-17 3:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4fa1c016-9fcb-b1ab-2df6-be774ac6344d@envisia.de \
--to=c.schmitt@envisia.de \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).