From: Benedikt Braunger <b.braunger@syseleven.de>
To: wireguard@lists.zx2c4.com
Subject: Wireguard in OpenVZ with NETIF_F_VIRTUAL feature
Date: Tue, 9 Jul 2019 10:30:44 +0200 [thread overview]
Message-ID: <e332179c-68e7-46f4-1f4c-7c6b899b0864@syseleven.de> (raw)
Hello Wireguards,
I've been testing wireguard with OpenVZ/Virtuozzo containers [1] which
is based on CentOS and figured out that it is not possible to create a
wireguard net interface within a container. However it is possible to
create it on the host machine and then move it to the containers network
namespace.
I contacted the Virtuozzo Support about this behaviour and they figured
out the reason and released a workaround with a wireguard patch [2]
I have two requests now
* can someone explain me why the `NETIF_F_VIRTUAL` feature is missing in
[3]? Is this somehow purpose?
* if not, would anything object to merge a patch like this to Wireguard?
Thanks in advance!
Beni
[1] https://de.wikipedia.org/wiki/OpenVZ
[2] https://wiki.openvz.org/VPN_using_Wireguard
[3] https://github.com/WireGuard/WireGuard/blob/master/src/device.c
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-07-17 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 8:30 Benedikt Braunger [this message]
2019-07-17 20:54 ` Wireguard in OpenVZ with NETIF_F_VIRTUAL feature Jason A. Donenfeld
2019-07-17 21:00 ` Jason A. Donenfeld
2019-07-17 22:41 ` Benedikt Braunger
2019-07-19 15:25 ` Jason A. Donenfeld
2019-07-19 16:44 ` Benedikt Braunger
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=e332179c-68e7-46f4-1f4c-7c6b899b0864@syseleven.de \
--to=b.braunger@syseleven.de \
--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).