From: Edward Vielmetti <edward.vielmetti@gmail.com>
To: WireGuard@lists.zx2c4.com
Subject: Wireguard + anycast
Date: Thu, 3 Jan 2019 17:36:45 -0500 [thread overview]
Message-ID: <CAPRZce1x-TLHiZ=nU9s0_aYcWZdf_hTbcXYg+ZkAjD1F_=X9ng@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 820 bytes --]
A little thought experiment which I haven't tried yet.
Using anycast, a single IP address can be routed to multiple machines in a
data center or around the world.
Is it at all possible that anycast and Wireguard would play together
nicely? In particular, is it plausible that you could give a client an
anycast address of a server to use as its endpoint, and that when it picked
the correct / closest one that it would do the right thing?
The naive approach would be to have all of the anycast devices share the
same private/public key pair, but that has a bad smell. And I don't know
what would happen if your routing changed in mid-connection.
(anycast is the technology used to give name servers a single global
address, like Google's 8.8.8.8 DNS)
--
Edward Vielmetti +1 734 330 2465
edward.vielmetti@gmail.com
[-- Attachment #1.2: Type: text/html, Size: 1244 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-01-03 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 22:36 Edward Vielmetti [this message]
2019-01-04 3:17 ` Wireguard + anycast David Cowden
2019-01-05 17:39 ` Phil Hofer
2019-01-04 8:30 ` Henning Reich
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='CAPRZce1x-TLHiZ=nU9s0_aYcWZdf_hTbcXYg+ZkAjD1F_=X9ng@mail.gmail.com' \
--to=edward.vielmetti@gmail.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).