Protections

The 16 one-click protections of the Edge Firewall, what each one does, and its settings and defaults.

PlaySafe Team · Firewall Management · Updated

Protections

The Protections tab of the Edge Firewall has 16 ready-made protections. Each one has an on/off switch, and some have settings. They are grouped in Network, TCP, Rate limits, Access and Payload.

Open it from Security > Firewalls, click the firewall and open Protections.

When you turn a protection on, the rules it needs appear in the Rules list, locked and marked “From” and the protection name. You manage them here, not from the list. Protection rules count toward the limit of 50 rules per firewall.


Network

ProtectionWhat it doesSettings (default)
Bogon sourcesDrops traffic from private and reserved addressesNone
IP fragmentsDrops fragmented IP packetsNone
Invalid packetsDrops malformed packets and ones that belong to no connectionNone
ICMP rate limitLimits ping and other ICMP trafficRate (1/s), Burst (5)

TCP

ProtectionWhat it doesSettings (default)
TCP flagsDrops packets with impossible TCP flag combinationsNone
New without handshakeDrops new TCP connections that do not start with a handshakeNone
Suspicious MSSDrops connection attempts with an unusual or missing segment sizeMinimum MSS (536), Maximum MSS (65535)
RST rate limitLimits TCP resetsRate (2/s), Burst (2)
SYN proxyAnswers connection handshakes for your server during SYN floodsNone

SYN proxy and New TCP connections cannot be on at the same time.


Rate limits

ProtectionWhat it doesSettings (default)
Connections per IPCaps open TCP connections per source addressMax connections (111)
New TCP connectionsLimits how many new TCP connections arrive per secondRate (60/s), Burst (20)
UDP rate limitLimits incoming UDP packetsRate (100/s), Burst (200)
!

Set the UDP limit above your game's traffic

**UDP rate limit** drops packets above the rate you set. Set it above what your game normally receives, or real players will be cut off.

Access

ProtectionWhat it doesSettings (default)
Close accessOnly your own IP and your allowlist can reach the serverYour IP and the allowlist (see below)
SSH brute forceBlocks addresses that keep trying to log in over SSHAttempts (10), Window (60 seconds)
Port scansSlows down and blocks port scannersNone

Close access

When you turn Close access on, your current IP is added for you. If your IP changes, click Use my current IP to update it. You can add more IPs or ranges, for example the office of a teammate. Everyone else is dropped.


Payload

ProtectionWhat it doesSettings (default)
Payload matchDrops packets whose payload contains a text you chooseProtocol (UDP or TCP), Port, Text to match, Action (Drop or Allow)

Settings and rates

  • Rates are written as a number per second, minute or hour: 10/s, 100/m or 5/h.
  • Changing a protection’s settings and saving applies it again.

Like rules, every change is applied to the server right away, and the panel shows Applying until the server confirms. If something fails you see the error and a Try again button; what was already running keeps running.


Where protections run

Each rule a protection creates shows a small XDP or Kernel tag in the Rules list, so you can see where it runs. moat follows connections itself, so the protections run in XDP, in the network driver, before the Linux network stack. The SYN proxy is the one that runs in the kernel, right after moat.


Next steps