From: Saeid Akbari <saeidscorp@yahoo.com>
To: wireguard@lists.zx2c4.com
Subject: Channel/Tunnel bonding with wireguard
Date: Tue, 23 Jan 2018 00:33:27 +0330 [thread overview]
Message-ID: <2657672.Dq05pOSN56@scorpbook> (raw)
Hi folks,
I have been thinking about utilizing WireGuard on my VPS to act as a central
hub for combining my multiple slower connections and having a faster one. I
had a possible way of doing it in my mind, and finally today I did a little bit
of googling found this article (also learned the real name for the technique:
bonding):
http://vrayo.com/how-to-set-up-a-bonding-vpn-connection-in-linux/
Since this approach uses a user-space daemon to relay around data, it would
incur some performance penalties compared to a kernel-mode driver like WG. So
it's probably not a good idea to use it on top of WG.
The pure WG scheme I have in my mind goes something like this:
- having a single swg0 interface on VPS.
- having multiple interfaces on the client (cwg0, cwg1, ...), each configured
with a single peer, that is the VPS swg0 interface.
- some iptables + ip rules fu to split and re-join the stream of IP packets.
For the third part, I can think of statistic netfilter match for splitting the
packets. But there are other things around which I don't know much about; like
the qdiscs... so I'm not confident if I'm headed in the right direction...
Is this a good idea? What do you suggest? Is there any better way to do it?
Thanks in Advance
Saeid,
next reply other threads:[~2018-01-22 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 21:03 Saeid Akbari [this message]
2018-01-23 1:16 ` WireGuard porting to kernel 3.4 JuniorJPDJ
2018-11-06 8:42 Channel/Tunnel bonding with wireguard GMX John Thomson
2018-11-06 20:51 Saeid Akbari
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=2657672.Dq05pOSN56@scorpbook \
--to=saeidscorp@yahoo.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).