Path Panel Filter Rules Guide

Path Panel Filter Rules Guide

Path Panel is the filtering system that provides network-level DDoS protection in the REXE infrastructure. It filters traffic before it reaches your server, protecting your server resources while delivering legitimate traffic without interruption.

How to Create a Filter Rule

1. Log in to Path Panel
2. Click on your server IP on the IP Management page
3. Click the Create New Rule button
4. Fill in the following fields:

5. Save the rule and wait for it to reach propagated status (2-5 min)

Default State and Default Block

When an IP address has no rules at all (not a single rule, including filter rules, ICMP/ping, and presets), all ports are open by default. In this state there is no Default Block.

The moment you create your first rule (even a single one), the system automatically adds a Default Block policy. From that point on, only the ports allowed by your rules stay open; all other ports are closed. When you delete all rules (including ICMP/ping and presets, so that not a single rule remains), Default Block is automatically removed and the IP returns to having all ports open.

You need to create a separate filter rule for each port you want to use.

Supported Filters

Game Filters

Game filters work by understanding the packet structure of each game protocol. They allow legitimate player connections while blocking attack traffic.

Application Filters

Filter Selection Guide

Standard Filter and Hard (L7) Filter

All filters below are Layer7 hard filter options: each recognises the packet structure of its protocol and tracks connection state. Filter rules are managed from the REXE panel; for each port you define either a standard rule or a suitable L7 filter.

There are two modes when creating a rule. In the standard filter you enter only protocol and port; that rule is also filtered and tracks connection state. In the hard filter you select one of the game or application filters above. State tracking exists in both modes; there is no protection mode without state tracking.

The only difference of the hard filter is that application-specific packets are inspected from the application's initial handshake through the entire packet flow. Since standard filters achieve roughly 99.99% filtering success, the hard filter is rarely needed in practice. No filter is a WAF; none provide in-application security (SQL injection, XSS) — the scope is network and protocol level.

Example Rule Configurations

SSH Access

Protocol:         TCP
Destination Port: 22
Filter mode:      Standard
Description:      SSH access

RDP Access

Protocol:         TCP
Destination Port: 3389
Filter mode:      Standard
Description:      RDP access

Minecraft Java Server

Protocol:         TCP
Destination Port: 25565
Filter:           Minecraft Java Edition
Description:      Minecraft Java server

FiveM Server

# Rule 1
Protocol:         UDP
Destination Port: 30120
Filter:           GTA FiveM
Description:      FiveM UDP

# Rule 2
Protocol:         TCP
Destination Port: 30120
Filter:           TCP Service (Symmetric)
Description:      FiveM TCP

# Rule 3 (txAdmin)
Protocol:         TCP
Destination Port: 40120
Filter:           TCP Service (Symmetric)
Description:      txAdmin panel

OpenVPN Server

Protocol:         UDP
Destination Port: 1194
Filter:           OpenVPN UDP Server
Description:      OpenVPN VPN server