'wg syncconf' not removing keep alive once set

. Christian McDonald E: rcmcdonal...@gmail.com

Re: wg syncconf (and setconf) error when one or more endpoints is unresolvable

me > peer entry. > > This has worked well for our use case. WireGuard always starts. > > Lonnie > > [1] Ignore endpoint DNS failure > https://github.com/astlinux-project/astlinux/blob/master/package/wireguard-tools/wireguard-tools-0001-ignore-endpoint-dns-failure.patch > -- R. Christian McDonald E: rcmcdonal...@gmail.com

wg syncconf (and setconf) error when one or more endpoints is unresolvable

is completely possible to re-implement syncconf and setconf using explicit `wg set` calls as a workaround. Am I missing something here? Thanks, Christian -- R. Christian McDonald E: rcmcdonal...@gmail.com

Re: Certain private keys being mangled by wg on FreeBSD

btw) and not dishing out unclamped keys to begin with. On Sun, Jun 6, 2021 at 12:21 PM Jason A. Donenfeld wrote: > > On 6/6/21, Christian McDonald wrote: > > Would it not be better for wg to just fail outright instead of > > transforming a poorly generated key entered by

Re: Certain private keys being mangled by wg on FreeBSD

ors forget to clamp them. So what you're seeing is correct > behavior. -- R. Christian McDonald M: (616) 856-9291 E: rcmcdonal...@gmail.com

Certain private keys being mangled by wg on FreeBSD

/theonemcdonald/pfSense-pkg-WireGuard/issues/105 Best, -- R. Christian McDonald E: rcmcdonal...@gmail.com

Kernel Panic on FreeBSD 12.2 when downing an tunnel interface

addresses assigned to it. Any ideas? All the best -- R. Christian McDonald M: (616) 856-9291 E: rcmcdonal...@gmail.com