Rayhaan JaufeerallyandClaude Fable 5.1
b800e3a322
Routes were announced and withdrawn through an HTTP form, each tagged with a free-text owner and checked against an allow-list and a per-owner limit. That was the lab's interface, not a router's. Routes now come from 'originate' entries in the configuration file and are in the local RIB before any session starts. The local RIB holds one route per prefix with no notion of owners or policy. local_route_policy is gone from the configuration. The HTTP API keeps its GET endpoints (status, config, peers, originated and received routes, events, metrics). The announce, withdraw, wire-bytes and well-known-community endpoints are removed, and the status page loses the announce form, the community presets and the byte decoder. Community text parsing moves from the web crate to bgp-packet so the configuration can use it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
18 lines
417 B
TOML
18 lines
417 B
TOML
[package]
|
|
name = "bgp-web"
|
|
description = "HTTP API, event stream and metrics for the BGP daemon"
|
|
edition.workspace = true
|
|
|
|
[dependencies]
|
|
axum.workspace = true
|
|
bgp-packet.workspace = true
|
|
bgp-rib.workspace = true
|
|
bgp-server.workspace = true
|
|
eyre.workspace = true
|
|
futures.workspace = true
|
|
prometheus.workspace = true
|
|
serde.workspace = true
|
|
tokio.workspace = true
|
|
tokio-stream.workspace = true
|
|
tracing.workspace = true
|