1200 is unusably slow for anything. 9600 is a standard speed for serial 
consoles, and is less susceptible to noise, buffer overruns, and false 
BREAK detection than faster speeds (have had it happen when just plugging 
in cables at 115200).


-- 
  Sent from a phone, apologies for poor formatting.

On 11 December 2024 17:59:56 Vitaliy Makkoveev <otto@bsdbox.dev> wrote:

>> On 11 Dec 2024, at 15:12, Stuart Henderson <stu@spacehopper.org> wrote:
>>
>> 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.
>
> Why not 1200? Obviously you will have troubles with slow console.