Protection and activation
How the account panel relates to a real mitigation network.
The planned traffic path#
Upstream infrastructure must absorb volumetric attacks before they reach the proxy. Minecraft-aware software then validates and forwards legitimate connections.
This website is the control plane for accounts and configuration. Cloudflare website hosting is not a Minecraft TCP/UDP mitigation server.
Players -> protected ingress -> PacketShield filtering -> originCurrent status#
The service state is awaiting_provider. Protection is inactive, Java and Bedrock routing availability are false, and there is no assigned endpoint. The interface intentionally reflects these limits.
Before activation#
- Provision protected upstream infrastructure permitted to carry customer traffic.
- Deploy and verify TCP and UDP filtering and forwarding.
- Connect authenticated provisioning to the panel.
- Assign real ingress addresses and enforce capacity.
- Provide origin firewall instructions and verify connections.
- Connect monitoring before showing live player, traffic or attack metrics.
Local development#
Ubuntu on a local computer can be used to test filtering and routing software. It cannot stop an attack from saturating the home internet connection before packets reach the machine. No local laptop routing service is connected to PacketShield.