Commit graph

5 commits

Author SHA1 Message Date
Frederic Jung
e80fd0e453
Spicy chaos stretches exactly what an incident holds down
stretchInc() stretched anything ending on the same day: always the primary attack
(even when the incident was about another one, never the overlapping ones) and any
unrelated outage that happened to end then. It now finds the attack by i.atk and
everything else by the incident's ref, as clearInc() does, and saves allow the
longest stretched attack (11 days).
2026-10-28 20:19:41 +01:00
Frederic Jung
40e4c79139
Attacks keep their 12 biggest ingress ports and fold the rest, so saves stay small
Every attack stored every ingress port with traffic (over a thousand on a big
network), which grew the save from 272 KB to 1.8 MB with 14 attacks. The rest is now
one share at the victim, routed like the classic flood over its usual exits; old
saves are folded on load.
2026-10-28 20:16:20 +01:00
Frederic Jung
25e3e6db33
DDoS attacks are scored and SLA-charged at their victim only
ddosSf() took the worst service of every city with an ingress port, so on a big
network every attack counted as lost and charged SLA payouts to protected customers
anywhere. Held/lost, the SLA check and the far-scrubbing warning now look at the
attacked city.
2026-10-28 20:11:06 +01:00
Frederic Jung
675c63d561
Floods cross the backbone to their victim again, whatever order the POPs were built in
Each ingress slice gave its junk the ingress city as source, so a flood only filled
the port it came in on: it never loaded the backbone or the victim's router, as it
did before distributed ingress. Junk is now created at the victim, pinned to its
entry port, before any real traffic and in attack order, so S.pops order no longer
decides who gets a full port. A port the victim cannot reach still fills.
2026-10-28 20:09:18 +01:00
Frederic Jung
6d839102b5
Pinned attack flows route at their entry port's own rank, not a cone rank
base() now takes the target network; pinned junk has none, so coneOf() called every
PNI a cone route and the flood was routed late (behind real traffic) or not at all.
Pinned flows use the port's own rank (low preference still last), those ranks join
RSET, and the reference allocation in the routing test does the same.
2026-10-28 19:58:25 +01:00