From: Saeid Akbari <saeidscorp@yahoo.com>
To: GMX John Thomson <john.thomson81@gmx.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Channel/Tunnel bonding with wireguard
Date: Wed, 07 Nov 2018 00:21:32 +0330 [thread overview]
Message-ID: <1663832.AtHhDoWA3l@scorpbook> (raw)
Hey John,
Unfortunately no, I don't quite remember it, but each attempt failed somehow.
At first, I tried with a single swg0 interface on the server, which had two
peers with different ip addresses (cwg0 and cwg1 on the client machine). Used
qdiscs to split packets between the cwg0 & cwg1, but I couldn't manage to
combine them on the server-side.
Then went on with two swg0 and swg1 interfaces, each with a peer corresponding
to client cwg0 and cwg1, and bonded the two with a bridge on the server.
Again, because of different IPs, it really didn't make sense to the kernel to
see them as one, and I couldn't make it so. Eventually, I ran out of ideas and
gave up.
However, the VTrunkD really seemed promising. (it implements the bonding in
user-space, meaning it can actually work, and is more *smart* than a simple
qdisc, and takes into account the underlying connections' properties). But I
simply gave up on the whole idea, mainly because there was no longer a need
for such a thing, plus I didn't have the time to investigate it. You should
look into it though :)
Regards,
Saeid
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2018-11-06 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 20:51 Saeid Akbari [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-06 8:42 Channel/Tunnel bonding with wireguard GMX John Thomson
2018-01-22 21:03 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=1663832.AtHhDoWA3l@scorpbook \
--to=saeidscorp@yahoo.com \
--cc=john.thomson81@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.