Hi,
Is anything blocking this from getting merged into wireguard-compat?
Regards,
Beni
On 3/4/21 7:30 PM, Benedikt Braunger wrote:
> This patch adds an additional check for OpenVZ / Virtuozzo 7 custom
> kernels to ensure ipv6_dst_lookup_flow is defined.
> It also splits the very lon
This patch adds an additional check for OpenVZ / Virtuozzo 7 custom
kernels to ensure ipv6_dst_lookup_flow is defined.
It also splits the very long version checking into multiple lines for
better reading.
Signed-off-by: Benedikt Braunger
---
Since the error mentioned in "Wireguard DKMS bui
Hello Tunnelerz,
Again I'm having trouble to compile the newest Wireguard DKMS module for
the wonderfully frankensteined OpenVZ / Virtuozzo 7 kernel.
The problem occures when updating the wireguard-dkms package
[17:32:10] root@test ~ # uname -a
Linux test 3.10.0-1127.18.2.vz7.163.46 #1 SMP Fri N
Hi Jason,
thanks very much for your input. Yes I also realized that the
NETIF_F_VIRTUAL is a Virtuozzo specific thing and almost lost hope with
this.
However with your patch applied I get a failure at dkms build and lots
of warnings in the log that NETIF_F_LLTX is redefined.
I'm not familiar with
Works like a charm! I can compile without any problems and I get
2Gbits/s out of the box between to containers on different hosts.
Thanks a lot!
Beni
Am 19.07.19 um 17:25 schrieb Jason A. Donenfeld:
> How's this look?
> https://git.zx2c4.com/WireGuard/commit/?id=08f1bfe29a08d9f10f9fa4c47e07a3501a
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 net
