Invalid routes reporting

[pierky]

What about extending some of the ideas already reported for LG Alice to the route server itself?
In particular the "order a pizza whenever a specific route is filtered by" the route server.

I wrote a sort of proof of concept that - unexpectedly - I called invalid_routes_reporter (full doc here).

I'm thinking of making it a standalone repository and also of extending the invalid routes identification mechanism in order to handle cases where the reject cause BGP community is missing but only a generic "invalid route" BGP community is attached to the invalid route.

[stefanplug]

Ah nice! Alice indeed looks at specific BGP communities added by the BIRD filters, these filters also trigger specific log messages which then get analysed by logstash and further enriched by a simple python script which gets data from a database like on what what actual port/switch the advertising peer is connected etc, and then outputs it to Slack. This requires a lot of infra though, and it would be sweet to have this all in a standalone tool!

[pierky]

So, the script has been moved into a standalone repository.

I changed a few things on it and now it is no longer strictly dependent on ARouteServer.
Now it can be used with or without BGP communities that describe the reason that led a route to be considered as invalid.

Full docs here.

I'm considering to add another option: a BGP community to track the real announcing network pierky/invalidroutesreporter#2

With the cooperation of the route server it could represent an easier way to determine the actual advertisting peer.