On 17.05.2019 09:34, . . wrote:
Hi,
I am using WireGuard on a Raspberry Pi 3 B+ with Raspbian Stretch and
4.14.98-v7+ kernel.
Now this works great for me and is very efficient, however I tried to
add a lot of routes on one of the "spoke/client" nodes, 517 routes to
be exact.
If I do this, Wir
Hi,
I am using WireGuard on a Raspberry Pi 3 B+ with Raspbian Stretch and
4.14.98-v7+ kernel.
Now this works great for me and is very efficient, however I tried to add a lot
of routes on one of the "spoke/client" nodes, 517 routes to be exact.
If I do this, WireGuard stops working, tcpdump shows
Dears Roopesh & Jason,
Wireguard ios client works perfectly for me, thanks for the great work.
Here is a feature request, instead of resolve all domain via tunnel's dns
server, users may only need resolve particular domains.
Could you kindly consider allow end user to specify the value of
d
Hi,
However, if I am not mistaken the version of OpenVPN used in the test
> was a *Windows* build of OpenVPN3 with a wintun patch included.
Correct.
> That is not open source, is it? I'd *not* be in favour of writing
> community
> wiki pages on the non-open source version of OpenVPN.
>
That'
it will most probably get lost in mailing list.
can we add it to https://openvpn.net website ? something like "performance
testing" with full configs provided ?
ср, 15 мая 2019 г. в 18:49, Lev Stipakov :
> Hi guys,
>
> I made openvpn3 (required changes will be incorporated into main branch at
> s
Hi David, *
On 15/05/19 19:32, David Sommerseth wrote:
On 15/05/2019 16:49, Илья Шипицин wrote:
it will most probably get lost in mailing list.
can we add it to https://openvpn.net website ? something like "performance
testing" with full configs provided ?
Good idea, but maybe not the official
Hi,
I am experiencing an inexplicable high count of dropped packets between
2 wg nodes:
local node (0.0.20190123 in kernel mode on OpenWRT 18.06 with kernel
4.14.113)
> wg0: mtu 1420 qdisc cake state UNKNOWN
> mode DEFAULT group defau
> link/none promiscuity 0
> wireguard addrgenmode n
I ported the x86 approach to allowing SIMD in kernel mode, even in an
interrupt, to powerpc[1], but I couldn't help wonder if it would be
possible without disabling preemption.
The scheduler just has to check the per-cpu in_kernel_fpu, and if it
is set, save the fpu state of the kernel thread, sim
Only runs on the out-bound path, as the in-bound path is in an interrupt,
but that can be fixed in Linux.
Otherwise this is tested (with the VSX code enabled) on Power 9 (ppc64le).
Without this I get 2GiB/s over the loopback (so 4 GiB/s), and with this
I get 2.8 GiB/s (so 5.6 GiB/s), and more time
Unfortunately I am not seeing a speed up with this patch,
but it does decrease CPU usage.
Only (currently) runs on the outbound path, as the in-bound path is in
an interrupt, but that can be fixed in Linux.
v2: - Do not include the FPU version, as +10% performance on POWER8
(admittedly better
10 matches
Mail list logo
