Mitigation-panel protocols and rule types
Reference for TCP, UDP, ICMP and all visible presets: use cases, suggested ports, modes, limits and restricted options.
Updated 8/3/20264 min read
Solutions
Cloud & Hosting
Infrastructure
Reference for TCP, UDP, ICMP and all visible presets: use cases, suggested ports, modes, limits and restricted options.
Updated 8/3/20264 min read
| Protocols | Typical use | General option |
|---|---|---|
| TCP (6) | Session-based connections: web, login, Minecraft and TCP services | TCP Service |
| UDP (17) | Datagrams: games, queries and UDP services | UDP Generic Port |
| ICMP (1) | Network control and ping; no TCP/UDP ports | ICMP, all ports |
Related guide: How mitigation-panel rules work
ICMP is customer-visible and has no transport port. Drop All is visible and blocks all ports and protocols; use it only to deliberately cut access. DNS Server (Hosted), UDP Symmetric, UDP ISP, TCP Symmetric and Allow All are administrator-only and should not be expected in customer accounts.
Current code caps regular users at 80,000 PPS for TCP and 1,200 PPS for UDP/other protocols. Confirm the UI value because role or configuration may alter what is accepted.
| Modes and limits | Visible behavior | PPS |
|---|---|---|
| A — Allow | Allows rule matches | Not required |
| B — Block | Blocks after the configured threshold | Positive; visible maximum depends on protocol and account |
| R — Rate Limit | Limits rate to the configured value | Positive; visible maximum depends on protocol and account |
Use UDP Generic Port or TCP Service according to the actual transport. If it uses both, create separate rules.
Yes. They are different protocols; overlap is validated among rules of the same protocol.