From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Dynamic Adresses
Date: Wed, 29 Nov 2017 08:25:05 -0600 [thread overview]
Message-ID: <E07E3E01-926C-4BB1-8C89-E262A6528FB4@lonnie.abelbeck.com> (raw)
In-Reply-To: <20171129134417.GH2523@debian>
On Nov 29, 2017, at 7:44 AM, Georg Faerber <georg@riseup.net> wrote:
> On 17-11-29 14:40:25, Jason A. Donenfeld wrote:
>> On Wed, Nov 29, 2017 at 2:35 PM, Mytril <mytril42@posteo.de> wrote:
>>> Yes i have written a similar script for the german ubuntuusers.de =
wiki.
>>=20
>> Care to share?
>=20
In this season of sharing :-) last week I took Jason's reresolve-dns =
script as a reference and created a persistent background script =
"wireguard-monitor" that is started/stopped along side wireguard in our =
AstLinux project.
wireguard-monitor
=
https://github.com/astlinux-project/astlinux/blob/master/package/wireguard=
/wireguard-monitor
Currently wireguard-monitor only updates DNS endpoints when =
WIREGUARD_DNS_UPDATE=3D"yes" in the sourced /etc/rc.conf file. =
wireguard-monitor can be stopped by deleting the PIDFILE.
One minor improvement over Jason's example is only DNS endpoints are =
updated, I test for manual IPv4/IPv6 addresses. I also wrote it hoping =
someday [Peer-peername] will be a valid config syntax.
Note, there are several things specific to our project, such as we =
create /var/lock/wireguard.lock when wireguard is active, and we include =
/usr/lib/bash/sleep as a bash builtin, but there might be a few ideas to =
take away.
Lonnie
next prev parent reply other threads:[~2017-11-29 14:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 13:05 Mytril
2017-11-29 13:12 ` Jason A. Donenfeld
2017-11-29 13:35 ` Mytril
2017-11-29 13:40 ` Jason A. Donenfeld
2017-11-29 13:44 ` Georg Faerber
2017-11-29 13:46 ` Jason A. Donenfeld
2017-11-29 13:49 ` Georg Faerber
2017-11-29 14:25 ` Lonnie Abelbeck [this message]
2017-11-29 13:47 ` Mytril
2017-11-29 13:54 ` Jason A. Donenfeld
2017-11-29 14:09 ` Mytril
2017-11-30 8:22 ` Mytril
2017-11-30 8:33 ` Mytril
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=E07E3E01-926C-4BB1-8C89-E262A6528FB4@lonnie.abelbeck.com \
--to=lists@lonnie.abelbeck.com \
--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).