pierky / invalidroutesreporter Goto Github PK

To track a BGP community that should be set by the route server on the basis of the announcing peer and that should represent its ASN.
It may be useful to correctly determine the network that announced an invalid route in case where both the leftmost ASN in the AS_PATH and the NEXT_HOP are wrong.

Example:

AS111 (whose peer IP address is 192.0.2.111) announces 1.0.0.0/8 with AS_PATH "222 333 444" and next-hop 192.0.2.222

Announcing network community: x:y:111, or rt:x:111

Dear Pier Carlo,

One of my bugbear with IX RS usage reports is that they tend to report the number of prefixes available at the exchange over time. I argue that this metric is useless (at least alone) as a /8 and /24 both count as a single entry.
As it is common for network to announce more-specific route to influence network routing, I would rather see reports of the numbers of unique smallest routable entries ( /24 for IPv4 - not sure from the top of my head for IPv6) present at the RS. Obviously, de-duplication of overlapping IP would need to occur.

Your mission @pierky, should you choose/decide to accept it, would be to implement a way to record currently announced unique /24 present at the RS to allow people to graph them over time.
Ideally the number reported should be per ASN.

A technical way would be to implement a new webserver exposing the data for a program like Prometheus to collect. Having used a similar approach (Prometheus export) for another project, I think it is a good way to go. Should you have any question, please contact me offline and I will share some code with you.

As always, should you or any of your team be caught or killed, the internet community will disavow any knowledge of your actions. This issue will self-destruct in ten seconds. Good luck @pierky