Secure Minecraft Java gameplay traffic, restrict administrator access, and prioritize legitimate server traffic through a guided protection workflow with optional QoS and OSSEC detection.
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.
Rule placement depends on the source and destination policy shape — not a blanket promise that everything runs in XDP.
When the QoS sidecar is available, Neurowall can prioritize Minecraft gameplay traffic using SQM/CAKE.
Each protection run is tracked as a separate instance so you can manage servers independently.
Removing protection for one instance does not delete unrelated server policies.
Neurowall shows the full proposed protection policy before it changes the firewall.
Neurowall provides host and network-edge protection, not full Minecraft protocol inspection or unlimited upstream DDoS absorption.
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.
Review the generated policy, confirm the enforcement layer, and apply protection with clear visibility into what changes.