Tie Flowspec filtering to the router's TCAM (1.17.1)
Flowspec was a flat network-wide licence. In reality the drop rules live in hardware TCAM, and the budget differs by platform, so flowspec is now a router-model capability: none on the used Rusty, a little on merchant-silicon and whitebox models, full on the big chassis. The flood is filtered only where the attacked POP's router can do it, and a bigger TCAM knocks it down further. The licence is gone; the NOC shows how many POPs are capable and the attack panel names the chassis doing the filtering.
This commit is contained in:
parent
c3b99df788
commit
5036f1a5a8
6 changed files with 76 additions and 56 deletions
|
|
@ -6,6 +6,15 @@ All notable changes to this project are documented here. The project follows
|
|||
|
||||
## [Unreleased]
|
||||
|
||||
## [1.17.1] — 2026-10-25
|
||||
|
||||
- Flowspec is now a property of your router, not a licence you buy once. The
|
||||
drop rules live in hardware (TCAM), and the budget differs by model: the
|
||||
used Rusty Router can't do it at all, merchant-silicon and whitebox models
|
||||
filter a known flood part-way, and the big chassis knock it right down. The
|
||||
NOC shows how many of your POPs are Flowspec-capable, and the live attack
|
||||
panel names the router doing (or not doing) the filtering.
|
||||
|
||||
## [1.17.0] — 2026-10-25
|
||||
|
||||
- DDoS attacks now have a shape: a vector (DNS reflection, NTP or CLDAP
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue