On 2026-01-19 19:48 UTC, Klemens Nanni <[email protected]> wrote:
> 18.01.2026 09:04, Miod Vallat пишет:
>>>> No message prior entering ddb?
>>>
>>> Console wasn't connected at that time, the the ddb prompt whas
>>> the first i saw after attaching and hitting enter.
>> 
>> Then, next time, run "dmesg" from ddb to get the complete kernel message
>> buffer; the last few lines should be the reason why it has entered ddb.
>> 
>
> Nothing besides nd6 spam (about addresses of non-OpenBSD devices that work 
> just fine):
>
> ddb{0}> dmesg
> <7>nd6_resolve: xxxx:xxxx:xxxx:xxxx:397f:4b51:7bcb:c6ff: incorrect nd6 
> information

Huh, I'm curious how the neighbour table looks like for this node. This
seems like one of those things that can't happen. (It's in nd6_resolve()
in nd6.c)

-- 
In my defence, I have been left unsupervised.

Reply via email to