Hi All - I'm trying to set up a WireGuard tunnel via udp2raw. The
client side is running Windows, the server is the linuxserver docker
container
I can get the tunnel set up through udp2raw, I can ping across it, I
can use mosh across it, I can sometimes do ssh, but I can't get HTTP
either with a
Kyle Sanderson writes:
> hi wireguard,
>
> APU2C4 - AMD Embedded G series GX-412TC, 1 GHz quad Jaguar core with
> 64 bit and AES-NI support
>
Um, I don't recall any Rijndael/AES in WG implementation, any particular
reason for mentioning AES-NI?
best,
evrim.
On 2022-10-25 2:58 a.m., Kyle Sanderson wrote:
hi wireguard,
APU2C4 - AMD Embedded G series GX-412TC, 1 GHz quad Jaguar core with
64 bit and AES-NI support
There has to be a way to improve this. I'm getting 20-40MB/s (causing
a system load of 6 on this poor box) where SSHFS in comparison is
From: Kyle Evans
Primarily, front-load validation of an allowed-ip entry to before we
allocate `aip`, so that we don't need to free() it if we end up skipping
this entry. Assert that `aip` is NULL after we exit the loop, as we
should have transfered ownership to the `peer` or freed it in all
From: Kyle Evans
The `err` path in kernel_set_device() will attempt to free() allocated
nvl_peers, but these two cases meant we could end up attempting a use
after free or a double free, as we rely on nvlist_destroy(NULL) being
a NOP as well as free(NULL).
FreeBSD-Coverity: 1500421
hi wireguard,
APU2C4 - AMD Embedded G series GX-412TC, 1 GHz quad Jaguar core with
64 bit and AES-NI support
There has to be a way to improve this. I'm getting 20-40MB/s (causing
a system load of 6 on this poor box) where SSHFS in comparison is
still able to fly. Traffic not traversing the
