InvalidRoutesReporter
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.
For more information: https://invalidroutesreporter.readthedocs.io
Change log
v0.2.0
New: --rejected-route-announced-by-pattern argument, to track a BGP community set with the peer that actually announced the invalid route.
New: --peer-asn-only option, to send alerts only to the peers that announced invalid routes.
v0.1.0
First release as a standalone repository.
New: make the reject reason BGP community optional and track also routes tagged with a reject BGP community only.
New: optional external file containing the reason-code/description matrix.
Fix: extended BGP communities processing.
Improvement: min_wait and max_wait timers handling.
1 maintainer
Metadata
1 maintainer
Release files for invalidroutesreporter 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| invalidroutesreporter-0.2.0.tar.gz | 25.3 kB | Without provenance | Details for invalidroutesreporter-0.2.0.tar.gz |
Release files / invalidroutesreporter-0.2.0.tar.gz
| Download URL | invalidroutesreporter-0.2.0.tar.gz |
|---|---|
| Size | 25.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e06da3f0e10b9c7d2eb1518e0249b5797ed8168baf39d5dac6dd16499b21cbe
|
|
BLAKE2b-256 checksum How to use checksums |
1054442c26ad0dd0ae8f22507438a128ede10ad5e49775b54e37f425a6bd5365
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for invalidroutesreporter 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
