From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Alex Besogonov <alex.besogonov@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Multihoming?
Date: Sun, 5 Apr 2020 01:38:17 -0600 [thread overview]
Message-ID: <CAHmME9rVRofNPx=Od3JZym-y=Jd1nN=_hZ9y9BOtNenofU0C1w@mail.gmail.com> (raw)
In-Reply-To: <445BCA5B-03B7-4127-82E8-029188083D45@gmail.com>
On Sat, Apr 4, 2020 at 4:45 PM Alex Besogonov <alex.besogonov@gmail.com> wrote:
> By true multihoming I mean possibility of using multiple connections at the same time, preferably with configurable rates for them on both sides.
Both connections at the same time, configurable rates... seems a bit
out of scope for an encrypted tunnel, doesn't it?
Rather, set up two tunnels, and then bond them or run some other
aggregation protocol over it. Several years ago I was aggregating
several different internet connections using MPTCP over various pipes.
Things worked extraordinarily well.
prev parent reply other threads:[~2020-04-05 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 7:22 Multihoming? Alex Besogonov
2020-04-05 0:47 ` Multihoming? Justin Kilpatrick
2020-04-05 7:38 ` Jason A. Donenfeld [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='CAHmME9rVRofNPx=Od3JZym-y=Jd1nN=_hZ9y9BOtNenofU0C1w@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=alex.besogonov@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).