Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Davide Depau <davide@depau.eu>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Multiple endpoints with same public key
Date: Mon, 3 Dec 2018 09:22:49 +0000	[thread overview]
Message-ID: <CAMp63jULeauEWi7KZzkOPTP+mphjo1FB-4=Mv6n4K3B1=kCT6w@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1515 bytes --]

A few days ago I was struggling with a very slow connection and I was
wondering whether WireGuard can support this setup (please see attached
graph).

There is a WireGuard server (the port it's listening on is reachable from
the outside), then one client with two interfaces connected to the Internet
with two different IP addresses.

Is it possible to have *one* WireGuard interface on the client, which sends
packets to the server through both interfaces in a round-robin fashion? I
would expect the server to detect the client (identified by the public key)
is sending packets from multiple endpoints, and send packets to both
endpoints.

If that's not possible with the current implementation (it should not as it
would break roaming), can it be implemented as a new feature?

One solution that keeps roaming working would be to explicitly enable the
multiple endpoints feature for each peer in the config file. If it's
enabled, keepalive packets are always sent at a configurable rate on both
ends and, when they don't get acknoweledged from one endpoint, it is
discarded.
If the feature is not enabled, the peers behave as they do now.

I'm not sure how the peer with multiple outgoing interfaces could be
configured to use all of them, though. I'll just leave this here so if you
think the idea might be good somebody may come up with a solution.
-- 

--

Davide Depau
PoliEdro <https://poliedro-polimi.it/> – PoliMi Pride <https://polimipride.it/>
Cell: +39 327 798 7963

[-- Attachment #1.2: Type: text/html, Size: 2659 bytes --]

[-- Attachment #2: drawing.pdf --]
[-- Type: application/pdf, Size: 12149 bytes --]

[-- Attachment #3: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2018-12-03  9:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03  9:22 Davide Depau [this message]
2018-12-03 13:11 ` Toke Høiland-Jørgensen

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='CAMp63jULeauEWi7KZzkOPTP+mphjo1FB-4=Mv6n4K3B1=kCT6w@mail.gmail.com' \
    --to=davide@depau.eu \
    --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).