seriesoftubes/site/i18n
Frederic Jung d56039695c
Attacks arrive as on 1.36 again: drop the distributed multi-ingress flood model
Frederic's call for 2.0: keep #153's fixes, NOC breakdown, new vectors, gaming risk
and overlapping attacks, but not the per-port model. It split every flood over each
ingress port with traffic (over a thousand on a big network), stored them all in the
save, routed one pinned flow per port, and with it came the build-order and
victim-scoring bugs found in review.

Each attack is again one entry port at the victim (a.entry): upstream clean-pipe,
Flowspec on the victim's router, IX blackholing, a sacrificial PNI and RouteScript
filter it in that order (ddosMitigation), then scrubbing; what leaks is junk at the
victim spread like its traffic, exactly as on main. Saves from 2.0 builds with
a.entries load: sanitize drops the shares and a 'distributed' entry becomes 'edge'.
Removed: R.ingressPorts, ddosEntries/ddosFold/ddosSlices/ddosCities/ddosHasIx, pinned
flows (and the pinned-rank handling in routing and its reference), the mixed-TCAM
line and the 'across N ports' message, and their tests; the scrubbing source-city
test now uses two victims sharing one center. CHANGELOG #153 bullets describe what
ships and credit #153.
2026-10-28 20:53:58 +01:00
..
de.js Attacks arrive as on 1.36 again: drop the distributed multi-ingress flood model 2026-10-28 20:53:58 +01:00
es.js Attacks arrive as on 1.36 again: drop the distributed multi-ingress flood model 2026-10-28 20:53:58 +01:00
fr.js Attacks arrive as on 1.36 again: drop the distributed multi-ingress flood model 2026-10-28 20:53:58 +01:00
it.js Attacks arrive as on 1.36 again: drop the distributed multi-ingress flood model 2026-10-28 20:53:58 +01:00
pt.js Attacks arrive as on 1.36 again: drop the distributed multi-ingress flood model 2026-10-28 20:53:58 +01:00