Keep game traffic available, prioritize legitimate players, and reduce unwanted network traffic before it reaches your servers. Neurowall combines firewall enforcement, eBPF/XDP acceleration, nftables policies, optional QoS, and OSSEC detection in one workflow.
A guided setup makes each proposed change visible before activation.
Neurowall shows whether each rule will be enforced through eBPF/XDP or nftables before anything is applied.
Allow gameplay traffic from trusted clients and restrict unwanted networks. Keep SSH administrator access separate.
When XDP is available, exact host-specific rules can be installed in the eBPF dataplane before traffic reaches the application.
CIDR and broader network policies use nftables when they cannot be expressed as exact eBPF host tuples.
Prioritize gameplay traffic with SQM/CAKE where supported. Existing enabled bandwidth profiles are reused rather than silently changed.
Workflow-created rules are grouped and labeled, so protection for one server can be reviewed or removed independently.
The review screen lists every important policy element before activation. No hidden rule generation and no silent truncation.
Neurowall provides host and network-edge protection. It does not replace upstream volumetric DDoS scrubbing or provider-level traffic filtering.
It provides a guided workflow for firewall enforcement, optional QoS prioritization, and optional OSSEC detection for selected game servers.
No. Exact host rules may use eBPF/XDP when available. Broader CIDR and unrestricted rules use nftables, and the review screen shows the placement.
No. Attacks that saturate an upstream connection require mitigation from an ISP, cloud, or upstream provider.
Yes. Workflow-owned rules are grouped and labeled so they can be reconciled and removed per protected server.
Review the generated policy, confirm the enforcement layer, and apply protection with clear visibility into what changes.