Protect Your Minecraft Server
with Neurowall.
Secure Minecraft Java gameplay traffic, restrict administrator access, and prioritize legitimate server traffic through a guided protection workflow with optional QoS and OSSEC detection.
Minecraft protection in a few steps.
What Neurowall protects.
The default Minecraft Java port is TCP 25565. Allow trusted player networks or leave the gameplay port public where appropriate.
Keep administrator access separate from gameplay. Restrict SSH to defined source IP addresses or networks.
Optionally define blocked networks and create explicit drop rules targeting the Minecraft service.
eBPF/XDP and nftables enforcement.
Rule placement depends on the source and destination policy shape — not a blanket promise that everything runs in XDP.
- Exact host sources can use eBPF/XDP when an XDP interface is attached
- CIDR networks use nftables
- Public or unrestricted service access uses nftables
- If XDP is unavailable, protection remains available through nftables
- The review screen shows each enforcement layer before activation
Optional Minecraft QoS.
When the QoS sidecar is available, Neurowall can prioritize Minecraft gameplay traffic using SQM/CAKE.
- Uses the selected interface
- Reuses an existing enabled QoS profile when possible
- Does not silently change existing bandwidth values
- Adds gameplay rules for the Minecraft port
- Reports QoS failures separately from firewall protection
Multiple Minecraft servers.
Each protection run is tracked as a separate instance so you can manage servers independently.
minecraft_02
minecraft_03
Removing protection for one instance does not delete unrelated server policies.
Review before activation.
Neurowall shows the full proposed protection policy before it changes the firewall.
- Minecraft server IP and selected interface
- Player, administrator and blocked networks
- Generated firewall rules
- eBPF/XDP or nftables placement
- Optional QoS actions
- Optional OSSEC actions
What Minecraft protection does not claim.
Neurowall provides host and network-edge protection, not full Minecraft protocol inspection or unlimited upstream DDoS absorption.
- No upstream volumetric DDoS scrubbing
- No Minecraft protocol-level inspection
- No guaranteed protection from uplink-saturating attacks
- No automatic remote-log collection without forwarding
- No automatic banning of shared-NAT player addresses
Related gaming protection.
Frequently asked questions.
- The current guided profile is for Minecraft Java.
- The default gameplay port is TCP 25565.
- Yes. The policy can permit public gameplay traffic when appropriate, while SSH administration remains separately restricted.
- No. If XDP is unavailable, the policy can be enforced through nftables.
- No. Logs must be accessible to the OSSEC host, such as through forwarding or a local mount.
- No. Use ISP, cloud, or upstream mitigation for attacks that saturate the uplink.
Protect your Minecraft server.
Review the generated policy, confirm the enforcement layer, and apply protection with clear visibility into what changes.