Development discussion of WireGuard
 help / color / mirror / Atom feed
* Channel/Tunnel bonding with wireguard
@ 2018-01-22 21:03 Saeid Akbari
  2018-01-23  1:16 ` WireGuard porting to kernel 3.4 JuniorJPDJ
  0 siblings, 1 reply; 2+ messages in thread
From: Saeid Akbari @ 2018-01-22 21:03 UTC (permalink / raw)
  To: wireguard

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,

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-01-23  1:13 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-01-22 21:03 Channel/Tunnel bonding with wireguard Saeid Akbari
2018-01-23  1:16 ` WireGuard porting to kernel 3.4 JuniorJPDJ

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).