From: Claas Langbehn <claas@rootdir.de>
To: wireguard@lists.zx2c4.com
Subject: Wireguard roaming - ARP?
Date: Mon, 11 Jan 2021 17:34:50 +0100 [thread overview]
Message-ID: <9a55e4b8-39eb-9705-5775-1aa3d5663ca6@rootdir.de> (raw)
Hello,
my wireguard setup is a triangle setup with
PEER A = fixed IPv4/IPv6 addresses
PEER B + PEER C = dial-up with dynamically changing IPv6-addresses.
To initially start the link between B and C it is neccessary to tell one
of them the others endpoint address. I do that manually, because it does
not make any sense with the dynamic addresses.
With the keep-alive option the wireguard vpn survives more that 99%, but
now I had a case where it failed:
B had a power loss at night (90 mins) and after the return of the power
it did not know the endpoint of C any more. So it cound not send packets
to C.
C could not send packets to B any more, because the endpoint addresses
also changed due to the power loss (the CPE had a power loss too).
This is why the link between B and C stopped working (could not be
recovered).
I could start using dyndns to solve this, but since I am using a
triangle setup: Would'nt it be nice if there would be some kind of ARP
between the clients? A always knows the vaild peer endpoint addresses of
my VPN. B/C could ask A about each others endpoint address. What do you
think? Would this be a nice feature?
Many regards
Claas
reply other threads:[~2021-01-11 23:30 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=9a55e4b8-39eb-9705-5775-1aa3d5663ca6@rootdir.de \
--to=claas@rootdir.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).