Merge latest main into codex/ddos-scaling-and-mitigation

This commit is contained in:
Filip Hruska 2026-10-27 10:19:38 +00:00
commit 330dbd5935
3 changed files with 9 additions and 5 deletions

View file

@ -16,8 +16,12 @@ All notable changes to this project are documented here. The project follows
- Each live attack in the NOC now shows incoming bandwidth, upstream scrubbing, edge filtering, scrubbing-center use and any traffic still leaking through.
- DDoS bandwidth now adds up: upstream scrubbing, edge filters and scrubbing centers work in sequence. The NOC uses the same figures as traffic routing, including floods that cannot reach a remote center.
- Attacks can now use Memcached amplification or an ACK flood. Flowspec catches the former; the latter need mitigation.
- Pick a peering policy in the peering inbox: Open to all, Selective or Closed. Open accepts every request and keeps the route servers; Selective gets fewer requests but you answer them yourself and request peers at each exchange, without route servers; Closed gets no requests, and customers hear you are hard to reach. The inbox also gets a button to raise all max-prefix limits at once.
- Brazil is slimmer: 15 small cities that sat right next to bigger ones are gone from new games, leaving 25 in Brazil. A small city no longer crowds a bigger one in the same country unless it is a cable landing or a capital. Saved games keep their POPs in those cities, and the Order and Progress scenario now asks for 15 IX.brrr ports instead of 20.
## [1.34.0] — 2026-10-27
- Choose your peering policy: Open to all, Selective or Closed. Open accepts everyone and keeps the route servers, Selective means fewer requests but you ask peers yourself, and Closed scares customers away.
- One button now raises every max-prefix limit at once. Leaks included.
- Brazil is slimmer: 15 small cities next to bigger ones are gone from new games. Saved games keep their POPs there, and Order and Progress now needs 15 IX.brrr ports.
## [1.33.0] — 2026-10-27