Open accuris-infrastructure opened 6 months ago
Also worth noting that even with the community being tagged, if you also have RPKI and IRR filtering enabled on the peer it also rejects the announcement due to being invalid or outside the prefix list.
Describe the bug Pathvector rejects routes with a length of /128 or /32 from peers when tagged with the blackhole community, when
filter-prefix-length
andallow-blackhole-community
are enabled on the session. It should be possible to allow these prefix lengths through the filters when tagged with the blackhole community, as some carriers only accept /32s and /128s for RTBH purposes.Environment
To Reproduce Steps to reproduce the behavior:
filter-prefix-length
andallow-blackhole-community
enabled on the peer.I suspect that this is due to the order in which the filters get processed in the generated BIRD config:
Expected behavior Blackhole gets processed as normal.
Actual behavior Blackhole gets rejected due to being out of bounds.