What problem does it solve?
BGP route hijacking and accidental route leaks occur because routers traditionally accept any prefix announcement without verifying the origin AS is authorized. This Skill guides you through deploying RPKI-based Route Origin Validation so your routers cryptographically verify announcements and reject invalid routes.
Core Features & Use Cases
- ROA Creation: Step-by-step instructions for creating Route Origin Authorizations through RIR portals (ARIN, RIPE NCC) with correct max-length settings to prevent sub-prefix hijacking.
- Validator Deployment: Install and run Routinator as an RPKI validator/cache serving VRPs over the RTR protocol, with systemd service configuration.
- Router ROV Configuration: Ready-to-use route-map and policy configurations for Cisco IOS-XE and Juniper Junos that accept Valid, depreference NotFound, and reject Invalid routes.
- Use Case: A network operator wants to protect their AS from prefix hijacking. They create ROAs for their prefixes, deploy two Routinator validators, apply RPKI filtering policies to all eBGP neighbors, and monitor validation state with the included Python monitoring script.
Quick Start
Ask the AI to walk you through creating a ROA for your prefix at your RIR and configuring RPKI route origin validation on your Cisco or Juniper BGP routers.