filter route and AS (possible feature request) about bgpq3 HOT 2 OPEN

Principle: when peering with 64500, it sends me its own routes, plus the routes of their customers. Due to frequent configuration error, 64500 sends me route of Customer 64510 as their own. This leads to potential routing problems, but also extended troubleshooting on my side, as this route is obviously filtered in some places. Is there a possibility to output further filters, when querying for an as-set, to have the routes group by orgin AS? This would immediately filter those wrong announcements. From my current point of view (as I'm using JunOS), this could be easily accomplished with a configuration block a this: # show | compare [edit policy-options] + policy-statement PERMIT-AS64500-IN { + term AS64500-ROUTES { + from { + as-path AS64500; + route-filter 192.0.2.0/24 exact; + } + } + term AS64500_AS64510-ROUTES { + from { + as-path AS64500_AS64510; + route-filter 10.0.0.0/23 upto /24; + } + } + } [edit policy-options] + as-path AS64500 64500+; + as-path AS64500_64510 "64500+ 64510+"; When included as import filter, this allows both networks to prepend their path as needed, but disallows an origin not documented in the RADB. I have multiple use cases for this filters, and I hope I'm not alone, with this, as I would have to script it externally (due to lack of skills in C). — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.*