This probably should get filtered out by babel if the interface is of wireguard
type?
Hmm, yeah, I think we could just ignore that particular error message in
all cases. The only way it appears on a regular UDP socket is if the
application sends a message without a destination address, which we
should never do.
Though it probably should be added to other protocols as well
(like the observed BFD spam).
Or in the babel case, such a message be considered as another signal that the
link is down, similar to `check link yes;`?
The problem with this is that there's no signal that the link comes back
up, so it's probably better to just ignore the error and keep going...
True, so better to ignore this send error / degrade to debug.
Florian
