How to handle 100Mpps+ DDoS traffic without exhausting your infrastructure
Handling 100Mpps+ requires an architecture designed for packet rate, not only for Gbps: early detection, upstream relief, fast filtering and clean traffic delivery.
Anti-DDoS software and filtering architecture.
Software, packet-processing framework, server and network capacity are separate choices. Use these guides to define the filtering path, choose the right test conditions and document what the platform actually sustains.
Defense Fabric is licensed filtering software for your servers and network links. The licence does not add upstream bandwidth. A 100G or 400G port label is a physical link characteristic, not a measured mitigation result.
Suggested reading order
Separate the software components
Distinguish XDP execution modes, DPDK packet I/O and VPP forwarding from the detection and filtering policy built on them. A framework name alone does not describe a mitigation product.
Establish the packet and link budget
Count ingress and egress separately, record frame-size conventions and include the relevant small-packet scenarios. Qualify NIC queues, PCIe, NUMA, CPU and memory with the intended rules.
Test the complete filtering path
Validate clean return, stateful traffic, route changes and loss of a filtering node. Measure acceptable packet loss, connection behaviour and recovery before treating an aggregate capacity as deployable.
Guides in this section
13 guides13 / 13 guides
DDoS protection: hardware or software?
Compare placement, capacity, filtering policy, failure behavior and operating cost before choosing an appliance, software dataplane or managed protected transit.
What is a DDoS scrubbing center? Traffic paths, ownership and buying criteria
Understand what a scrubbing center does, what the advertised capacity does not establish, and how to choose between protected transit and your own filtering infrastructure.
How a DDoS scrubbing center works: attraction, filtering, delivery and recovery
Follow the operating chain with explicit authorization, matched observations, bounded policy changes and application checks before declaring recovery.
DDoS mitigation architecture: design the complete path
Map detection, routing, packet filtering and traffic delivery, then verify capacity, return paths, MTU and recovery before putting an architecture into service.
1Tbps DDoS mitigation: architecture, real limits and clean traffic handoff
A technical guide to what 1Tbps DDoS mitigation really means: upstream capacity, PPS saturation, BGP, FlowSpec, tunnels, cross-connects, clean traffic delivery and the mistakes to avoid before buying premium protection.
Custom XDP for DDoS: when it is worth building
Decide whether custom XDP solves your bottleneck, distinguish its execution modes and define the traffic, measurements and rollback needed before deployment.
Dedicated Anti-DDoS filtering server: what is it really for?
A dedicated Anti-DDoS filtering server separates production from the decision layer, enables more precise logic and keeps the existing stack behind it. This guide explains when the model makes sense, when it does not and how to place it cleanly inside the architecture.
Protected dedicated servers: define the responsibilities
Separate upstream protection, host firewall policy and application operations before exposing a service.
Build a filtering stack behind upstream mitigation
Assign transport protection, early packet checks, connection policy and application controls distinct duties, with a measurable path through each layer.
High-PPS filtering: examine receive queues and CPU placement
Inspect RSS distribution, memory locality and per-rule costs before adding processing cores.
How do you mitigate a DDoS attack above 100Gbps?
Mitigating a DDoS attack above 100Gbps requires far more than a large headline capacity number. This guide covers link saturation, PPS, CPU, upstream pre-filtering, dedicated filtering servers and clean traffic handoff to build a credible design.
XDP vs DPDK for Anti-DDoS filtering: which one should you choose?
The XDP vs DPDK Anti-DDoS question comes up all the time. This guide gives a practical answer for network and security teams: what XDP does extremely well, when DPDK becomes the right tool and which approach usually offers the best cost, performance and operations ratio.
No guide matches this search. Try a protocol name or a shorter phrase.
From architecture to a supported deployment.
The Defense Fabric guide documents the current installation and integration requirements. The comparison pages distinguish detection, filtering and orchestration components across vendors, with links to their sources.