C2b-1: FlowSpec auto-mitigation core (selection + controller + manager + gate) #86
Labels
No labels
bug
deploy
documentation
duplicate
enhancement
good first issue
help wanted
invalid
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
femboy/blackwall#86
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
First increment of C2b — a detection auto-becomes the right mitigation.
select()(blackwall-flow): a flow-concentrated attack → FlowSpec drop rules (drop the attack flow, victim's other services stay up); a diffuse attack → RTBH whole-IP blackhole.FlowSpecController+ single-ownerFlowSpecManager(blackwall-rtbh), mirroring the RTBH controller/manager (eligibility, cap, hold-down + deferred-withdraw + TTL, origin, mirror self-heal); shared iBGP session via an extendedBgpExecutor.SelectorSinkroutes each detection to the FlowSpec or RTBH manager.flowspec-auto-birdlab gate: concentrated → FlowSpec rule in real BIRD'sflow4tab; diffuse → RTBH/32blackhole — both auto-mitigation paths proven against real BIRD2.Codec-first cadence (C1b→C1c style). C2b-2 (persistence +
flowspecconfig directive +blackwalld flowspecCLI + daemon wiring) follows. Sub-project C, epic #6.