On Tue, Jun 8, 2021 at 1:00 PM ben edmunds wrote:
> By not showing this to the user to avoid confusion we actually would
> create confusion in this scenario as the kernel module is performing the
> clamping but the user would have no knowledge of this and leads to
> issues being opened that are a
The issue here for pfSense is that the private key will be viewable just
like it is within native wireguard clients in the peer config options
and needs to be viewable here for admin and debug purposes.
With regards to clamping and hiding this from users its tricky as it
leads to red heroin
I might encounter the same problem as
https://lists.zx2c4.com/pipermail/wireguard/2020-August/005801.html
When endpoint is set as 127.0.0.1:51820, the log shows like follows:
[TUN] [xxx] peer(xxx) Received handshake response
[TUN] [xxx] peer(xxx) - Retrying handshake because we stopped hearing
