| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
For $reasons, we can't rely on flags in wireguard-tools for the kernel
side of WireGuard. Provide a mapping function that uses flags from the
kernel that we're building against and fail the operation if we made it
to the end without turning some wg(8) flag off.
Signed-off-by: Kyle Evans <kevans@FreeBSD.org>
Reviewed by: ivy (previous version), Jason A. Donenfeld, jhb
Differential Revision: https://reviews.freebsd.org/D50450
|
| |
|
|
|
|
| |
Update wireguard-tools to the latest version, which has some stubbed out support
for incremental Allowed-IPs updates that we would need to add kernel support
for.
|
| |
|
|
|
|
|
|
|
|
|
| |
AF_INET assumes that IPv4 is built into the kernel, but it's completely
valid to build a kernel without it. unix(4) sockets, on the other hand,
are not-optional in the kernel build. Given that interface ioctls can
be invoked on any kind of socket, switch to the safer one to avoid
breaking on IPv6-only kernels.
Reported and tested by: ivy
MFC after: 3 days
|
| |
|
|
|
|
|
| |
This fixes a warning in wireguard-tools, as well as two issues pointed out by
FreeBSD's Coverity instance.
CID: 1500405, 1500421
|
|
|
'7e00bf8773b93a2a3ee28dba2710d2ae443989f1'
git-subtree-dir: contrib/wireguard-tools
git-subtree-mainline: 9142a2a37b2fe65d46ace08a098ad26b8ff81541
git-subtree-split: 7e00bf8773b93a2a3ee28dba2710d2ae443989f1
|