From: Stuart Henderson <stu@spacehopper.org>
Subject: Re: [patch] wireguard floods dmesg
To: Vitaliy Makkoveev <otto@bsdbox.dev>
Cc: Claudio Jeker <cjeker@diehard.n-r-g.com>, Lloyd <ng2d68@proton.me>,  "tech@openbsd.org" <tech@openbsd.org>
Date: Wed, 11 Dec 2024 12:12:12 +0000

On 2024/12/11 14:39, Vitaliy Makkoveev wrote:
> > On 11 Dec 2024, at 12:24, Claudio Jeker <cjeker@diehard.n-r-g.com> wrote:
> > 
> > On Wed, Dec 11, 2024 at 07:45:34AM +0000, Lloyd wrote:
> >> Hello,
> >> 
> >> Wireguard has a rudimentary logging function accessed by setting the debug flag on the interface. Logging Wireguard activity is desirable e.g. for SIEM purposes. However, the current implementation will flood the system message buffer with the following message if the other side of the tunnel is down:
> >> 
> >> wg0: No valid endpoint has been configured or discovered for peer 0
> >> wg0: No valid endpoint has been configured or discovered for peer 0
> >> wg0: No valid endpoint has been configured or discovered for peer 0
> > 
> > Is that message actually useful? Shouldn't it be simply removed?
> 
> This message appears only if IFF_DEBUG flag is set. No problem
> with it.

Try serial console with 9600bps and see if you still agree.