From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Lane Russell <lanerussell@protonmail.com>, david.w.cowden@gmail.com
Cc: wireguard@lists.zx2c4.com
Subject: Re: Configure WireGuard for Roaming Between IPv4, IPv6
Date: Sun, 16 Sep 2018 20:22:07 +0200 [thread overview]
Message-ID: <87mush8fqo.fsf@toke.dk> (raw)
In-Reply-To: <Ea_ThlFNfnz6b5yIEpIB8ZPryiwewgFtSFd-PyXbPB5vQZQ91Es-IjDzPAbJxuux3Zr8pTAtwC9X0M3GXw08pVyqrDIOQBnxIdmiS_-6y8Y=@protonmail.com>
Lane Russell <lanerussell@protonmail.com> writes:
> Since this is a home setup and my /56 might (will) change at some
> point, I don't want to have to reconfigure my router, server, and
> clients. Unless there's a way to dynamically reconfigure these devices
> in such a situation?
Ah, right; renumbering is a PITA. Hmm, you could tell your ISP to get a
clue and stop doing that? ;)
Otherwise I suppose it *may* be possible to run a DHCPv6 server on the
wireguard server. Assuming the clients have the server configured with
AllowedIPs=::/0, the DHCP request should get through to the server. So
as long as the DHCP daemon replies via unicast, it could work. You'd
need to manually configure a static link-local (fe80::/64) address for
each client, which can be used as a source address for a DHCP request.
And then have a trigger script on the wireguard server add the IP to
AllowedIPs for the peer when it assigns an IP. I think odhcpd (that is
used on OpenWrt) allows this at least.
Note I haven't tested this; but I *think* it could be made to work, with
a bit of tweaking :)
-Toke
prev parent reply other threads:[~2018-09-16 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 19:33 Configure WireGuard for Roaming Between IPv4, IPv6 Lane Russell
2018-09-15 22:41 ` David Cowden
2018-09-16 16:40 ` Lane Russell
2018-09-16 17:47 ` Toke Høiland-Jørgensen
2018-09-16 18:09 ` Lane Russell
2018-09-16 18:22 ` Toke Høiland-Jørgensen [this message]
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=87mush8fqo.fsf@toke.dk \
--to=toke@toke.dk \
--cc=david.w.cowden@gmail.com \
--cc=lanerussell@protonmail.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).