Rayhaan JaufeerallyandClaude Fable 5.1
cc022c3b7b
Modelled on Vitess's servenv status page and golang.org/x/net/trace, both written by Google engineers to mirror the internal pages: plain sans-serif HTML, default links and native form controls, dense bordered tables, and a full-width centred light blue (#eef) heading bar per section. Header shows "Status for ferrix_bgp" with start time, uptime, version, router ID and AS on the left and host, "View:" links and live-update state on the right. The dark theme is dropped on purpose. Behaviour is unchanged (live updates, owner-gated withdraw, per-session UPDATE bytes, looped-route highlight, peers polling). Additions: - a SwissIX large-community picker next to the field; presets with a peer AS ask for the number - event log lines include prepend and MED - /api/status gains hostname and started_at_unix (RouterInfo::new) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
BGP
The bgp crate is an implementation of the Border Gateway Protocol, which is used to exchange routing and control plane information between Autonomous Systms.
The aim of this project is to provide a modern, high performance, secure and programatic and customizable software package that can be useful to network operators, researchers, and people interested in Internet.
Current status.
The project is currently being rewritten from scratch to be more modular and maintainable, as well as to fix deeper issues with the previous implementation.
⚠️ Warning: This is currently a work in progress and not ready for use.
🛣️ Roadmap to v1.0
We aim for the 1.0 release to be functional and stable to operate peering sessions, and to install routes in the Linux Kernel.
- ☐ Implement basic parsers for the fundamental types required
- ✅ Path Attributes from RFC4271
- ✅ Open message
- ✅ Capabilities from RFC4271
- ✅ Update message
- ☐ Notification message
- ✅ Implement scaffolding required to start and configure a server
- ✅ Implement connection logic to establish sessions with peers (passive and active)
- ✅ Locally originated routes with communities, announced to all peers
- ✅ HTTP API, live status page and Prometheus metrics
- ☐ Implement an efficient data structure for storing prefixes (e.g. Poptrie)
- ☐ Filtering for peer RIB in / out
- ☐ Main / auxillary RIBs for exchanging routes between peers