Peter Piwowarski wrote:
> Steve Williams wrote:
>
> > I can see that the DEBUG flag is set, but how to I access that
> > debugging information?
>
> You should be seeing it spam dmesg pretty voluminously.
The current implementation of Wireguard debugging leaves a bit to be
desired. Not just spamming dmesg but the lack of detail. I have posted
an evolving patch against -current over on the tech@ list that moves
this data to syslog instead of printf(9) and adds IP address info of the
peers to the logging messages. One of the chief complaints of the various
implementations of Wireguard regardless of OS is the poor logging support.
It seems to be by design. I am cleaning up the patch based on feedback
from the developers and will post a cleaned up version shortly. My hope is
if merged it will provide an easy way to log Wireguard events. I believe
Wireguard logging under Linux is equally if not more painful, having to
enable dynamic debugging on the kernel module but I'm not familiar with it.
Regards
Lloyd
No comments:
Post a Comment