An ExaBGP process to elaborate and report/log invalid routes received by route servers.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs
example
pierky
scripts
tests
utils
.gitignore
.travis.yml
CHANGES.rst
LICENSE
MANIFEST.in
README.rst
build_networks_config_from_arouteserver.py
diagram.png
integration.png
setup.py
trigger_travis

README.rst

InvalidRoutesReporter

Documentation Build Status PYPI Version

This script is intended to be used as an ExaBGP process to elaborate and report/log invalid routes that have been tagged with meaningful dedicated BGP communities by route servers.

Invalid routes are those routes that, for some reason, didn't pass the route server's validation process (invalid/private ASNs in the AS_PATH, bogon prefixes, invalid NEXT_HOP, IRRDBs data mismatch, ...). Route servers, instead of discarding them, can keep these routes and tag them with a BGP community that describes the reason for which they have been considered as invalid.

A session with an ExaBGP-based route collector can be used to announce these invalid routes to this script, that finally processes them, extracts the reject reason and uses this information to log a record or to send an email alert to the involved networks.

If deployed in conjunction with ARouteServer, the "tag" reject policy option can be used to easily setup the route server to work together with this script.

diagram.png

For more information: https://invalidroutesreporter.readthedocs.io

Author

Pier Carlo Chiodi - https://pierky.com

Blog: https://blog.pierky.com Twitter: @pierky