Firstly, I am using Bird 1.6.3,. not 2.x. Secondly, I have tried to do that but failed to get the filter correct. Do you have any suggestions? These two opaque routes only exist in the LSADB - they dont show up in routes in BIRD or the mikrotik devices. From a post above, you can see the LSA type is coming in as 0000 (Bird doesnt recognize it)
I assume if it’s not implemented in 2.x it’s not in 1.x either, but I didn’t specifically check.
I looked through the BIRD source a little bit and I can’t find a reference to being able to filter by LSA type. It doesn’t appear to be documented. Maybe you can’t.
The LSA type being 0000 is weird because you’d expect it to be 9/10/11 if it’s formed correctly. It’s also possible that BIRD has an enum of the supported types that only goes up to 8 and it prints the log as 0 because it thinks the LSA is malformed. Hard to say. mrz has the right idea there to packet capture and future out whether the LSAs are actually malformed or whether it’s just an artifact of BIRD not understanding them.
In the end, is the problem that BIRD is polluting its logs with malformed LSA notifications? It’s probably not impacting the actual functionality, right? Also to mrz’s point if you aren’t actually using them, turning them off at the source is better. I was under the impression you were intentionally using them but that you just wanted to restrict their propagation to devices that didn’t understand them.