Most network security at the ISP edge happens too late. A flood crosses your core before a scrubbing appliance sees it; spoofed traffic is traced back hours after it left a subscriber port; an infected device is found when its upstream complaint arrives. XDP moves the decision to the earliest point Linux has: the network driver, before the kernel has spent any work on the packet. This is what that makes possible, and what it does not replace.
Why the driver is the right place to drop traffic
An XDP program sees each packet as raw bytes in the receive path and can return XDP_DROP before the kernel allocates anything for it. Dropping there costs a fraction of what it costs after the full network stack has run, which is why XDP is the standard tool for packet filtering at high rates. Every program is checked by the kernel verifier before it loads, so filtering rules can be updated on a live system without risking the machine.
Anti-spoof at the source
On a BNG, the data plane already knows which addresses belong to which subscriber session. Traffic leaving a subscriber port with someone else’s source address, or with a private-range address that should never appear, can be dropped where it enters rather than traced back later. That stops reflection and amplification attacks from being launched from your own network.
Per-victim DDoS containment
Chasing an attacker’s addresses does not work when the attack comes from thousands of them. Applying protection per subscriber and per attack type, at line rate, keeps the victim reachable while the flood aimed at them is dropped. Because the decision is made in the same data plane that forwards the traffic, there is no detour to a scrubbing centre and no added latency for clean traffic.
Block the attack, not the customer
The hard part of edge security is not blocking traffic; it is blocking an attack without taking the customer offline. Filtering in the forwarding path makes it possible to stop one offending flow while the rest of that subscriber’s traffic keeps running, and to contain a recruited device at its own port before its traffic crosses your core.
What it costs in CPU
Measured on BNGSOFT’s XDP data plane at production load, DDoS fanout takes about 2.5 percent of data-plane CPU, and spoof filtering, flood control and abuse drop together sustain around 7 percent while enforcing at line rate. Hardening is part of the same release cycle: OrionOS 7.05 closed DHCP ports 67 and 547 on the uplink and drops NULL-scan TCP in both modes.
What XDP filtering does not replace
- It does not add capacity. If an attack is larger than your upstream links, it has to be dropped upstream as well.
- It is not deep inspection. XDP works on headers and simple state; application-layer analysis belongs elsewhere.
- It needs good drivers. Native XDP mode depends on the NIC driver; generic mode is far slower and is not a production fallback.
Go deeper
- Edge security and DDoS: filtering in the same data plane that forwards.
- eBPF and XDP for ISPs: how in-kernel packet processing works.
- The XDP data plane: packet processing inside the Linux kernel.
- Request a proof of concept on your own hardware and traffic.
Go deeper
- Edge security and DDoS: filtering in the same data plane that forwards.
- The XDP data plane: packet processing inside the Linux kernel.
- eBPF and XDP for ISPs: how in-kernel packet processing works.
- Request a proof of concept: on your own hardware and traffic.


