From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Davide Depau <davide@depau.eu>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Multiple endpoints with same public key
Date: Mon, 03 Dec 2018 15:11:23 +0200 [thread overview]
Message-ID: <87k1kqkb5w.fsf@toke.dk> (raw)
In-Reply-To: <CAMp63jULeauEWi7KZzkOPTP+mphjo1FB-4=Mv6n4K3B1=kCT6w@mail.gmail.com>
Davide Depau <davide@depau.eu> writes:
> 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.
I think this would be better solved at a higher layer: Run two tunnels
(to two different port numbers on the server, for instance), and have
the kernel do ECMP routing across both wireguard interfaces...
-Toke
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2018-12-03 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 9:22 Multiple endpoints with same public key Davide Depau
2018-12-03 13:11 ` 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=87k1kqkb5w.fsf@toke.dk \
--to=toke@toke.dk \
--cc=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).