Hello, Speaking of logs, there are other logs that may (or may not) annoy some people: - “<RMT> bfd1: Bad packet from 37.49.xx.yy - unknown session id (nnnnnnnnn)” when it starts, it may easily get to 1 line / sec / session - "Route leak detected - OTC attribute from downstream” + one more line with the route itself. Needless to say about what happens when some smashed-fingers operator announces all routes from one RS (200K of them all with OTC) to the other RS This is just what comes to mind, I could look to see if I can find more. The point is that some events generate a log entry at each occurence, and when they start occurring, they may do it at high frequency, heavily polluting logs. We may not want to have those logs. Is there anything that can be done about it ? Regards, -- Radu-Adrian FEURDEAN Web : www.franceix.net
On 20 May 2025, at 14:53, Elmar K. Bins <elmi@noir.de> wrote:
Hi everyone,
I couldn't find anything in the docs, not much going on in terms of quenching log output. Also couldn't find any routecollector config examples that address this...so...
I'm running this BIRD 2.16.1 (out of pkg/quarterly) as a routecollector, hence it does not need any next hops for anything.
It is nicely telling me that "<neighbor-ip> resolvable through recursive route for <neighbor's-prefix>", which I don't want to know or see in my log - it's a huge load of entries .
Is there a way to quench this log message, and/or is there a way to fine-tune log output in BIRD?
Thanks, Elmar.