Path Panel DDoS Protection Management Panel User Guide
Complete REXE Path Panel user guide: Dashboard, My IPs, TR protection status, rule management, attack history, abuse filtered, password change and API access.
Table of Contents
Introduction
REXE Path Panel is the DDoS protection management interface offered to REXE Teknoloji customers. As a User (end user), you can manage the rules of the IP addresses assigned to you, monitor your attack history, and apply ready-made protection profiles through this panel.
Backed by Path.net's global 10Tbps+ network capacity, this system performs stateful filtering at the L3/L4 layer, ensuring that only legitimate traffic reaches your server.
You can access Path Panel directly at x.rexe.tr.
Dashboard
When you log in, the dashboard page opens. Only data belonging to the IP addresses assigned to you is shown here.
- Attack Summary: Total number of attacks over the last 15 days along with the highest BPS/PPS values
- Top 10 Attacked IPs: BPS, PPS and attack count statistics for your IPs
Only data for the IPs assigned to you is displayed on the dashboard. Other users' data is not visible.
My IPs
Menu: My IPs
You view the IP addresses assigned to you on this page.
IP List
| Column | Description |
|---|---|
| IP Address | IP address assigned to you |
| Protection | TR /32 protection status on the router |
| Default Block | Automatic blocking status (Yes / No) |
| Creation Date | Date the IP was added to the system |
- Using the globe icon (🌐) you can quickly view an IP's rules in a popup window
- You can sort, paginate and filter with search
- Using the Protection Status and Default Block filters you can filter IPs by their status
- Filters are stored in the URL; your selections are preserved even if the page is refreshed or the link is shared
- Click an IP address to go to that IP's rule management page
You do not have permission to add, delete or assign IPs to other users. IPs are assigned to you by your parent user (Reseller or Manager).
TR Protection Status
Each IP's Protection column shows the TR /32 protection status on the router:
| Status | Description |
|---|---|
| TR Protected | Protection active |
| TR Unprotected | Protection off |
| Queued | Operation queued |
| Applying | Protection enable operation in progress |
| Removing | Protection disable operation in progress |
| Error | Operation failed |
Protection status on this page is view-only. Enabling/disabling protection is done by your parent user (Reseller/Manager) or Admin.
Default Block
Each IP's default block status is shown as "Yes" or "No". Default Block is managed automatically by the system based on the rule state of your IP:
- When the IP has no rules at all (not a single rule, including filter rules, ICMP/ping and presets): all ports are open and there is no Default Block.
- The moment you add the first rule: the system automatically adds a Default Block. From that point on, only the ports allowed by your rules remain open, and all other ports are closed.
- When you delete all rules (if not a single rule remains, including ICMP/ping and presets): Default Block is automatically removed and the IP returns to having all ports open again.
| Rule State | Default Block | Result |
|---|---|---|
| No rules | None | All ports open |
| At least 1 rule | Added automatically | Only allowed ports open |
| All rules deleted | Removed automatically | All ports open again |
Default Block management is done by your parent user or Admin; on this page you only view the status.
Rule Management
When you click an IP address, the rule management page opens. On this page you manage the firewall rules belonging to your IP.
Existing Rules
| Column | Description |
|---|---|
| Filter | Applied DDoS filter |
| Protocol | TCP or UDP |
| Port | Target port number |
| Source | Source IP/range |
| Status | Rule synchronization status |
| Comment | Rule description |
Creating a New Rule
- Click the "New Rule" button
- Fill in the fields:
- Protocol: Select TCP or UDP
- Target Port: Enter the port number (between 1-65535, e.g. 80, 443, 25565)
- Filter: Select a filter from the list (required). Only the filters permitted to you are listed
- Comment: A note describing what the rule does (optional)
- Click the "Create" button
- The rule is automatically sent to Path.net
The rules you newly create appear at the top of the list. The rule creation screen has two modes: standard filter (protocol + port only) and hard filter (Layer7 filters like TCP Symmetric). For SSH, RDP, and most services the standard mode is enough; hard filter (Layer7) options like TCP Symmetric should only be enabled for highly sensitive applications. You can create rules from Path Panel (x.rexe.tr) or from the Rule Management product in your customer panel.
The moment you create your first rule, Default Block kicks in and all disallowed ports are closed. For this reason, be sure to include your management port such as SSH (port 22) or RDP (port 3389) in your first rule set; otherwise your connection to the server will be cut when the rule becomes active.
Enabling ICMP / Ping
The rule form does not have a direct ICMP option. To open ping (ICMP) traffic, use the "Ping On/Off" toggle at the top of the rule page. When the toggle is turned on, an ICMP rule is created automatically; when turned off, it is deleted.
Ping Toggle: OFF → ON
→ ICMP rule created automatically
→ Ping responds after the rule is published
If you want to send an MTR test or check server access with ping, you must first enable ICMP.
The ICMP/Ping rule also counts as a rule. When you turn on the Ping toggle while there are no other rules on your IP, Default Block kicks in automatically and disallowed ports are closed. Make sure you also create rules for your management ports (SSH/RDP).
Rule Statuses
| Status | Description |
|---|---|
| pending | Rule created, waiting to be sent to Path.net |
| synced | Rule successfully sent to Path.net |
| propagated | Rule propagated to all network nodes (full protection active) |
| failed | Submission failed — can be retried with the retry button |
Publishing a rule (propagating it to all network nodes) can take 2-5 minutes. During this period the rule gradually takes effect.
Even if the rule appears not yet propagated in the panel, it has most likely already been published within 2-5 minutes. Due to reasons such as the panel's status check interval, the status may update with a delay; this is only a visual delay, the port has actually already been opened in the system.
Deleting a Rule
Click the delete button next to the rule. The rule is removed from both the panel and Path.net.
Retrying a Failed Rule
A retry button appears next to rules in the "failed" status. By clicking the button you can resend the rule to Path.net.
Applying a Preset (Ready-Made Profile)
Presets let you apply frequently used rule combinations with a single click.
- Click the "Ready-Made Profile" button on the rule page
- Select a preset from the list (e.g. "Cloudflare Whitelist", "Game Server Protection")
- All rules in the preset are applied to your IP in bulk
Preset rules are shown grouped in the table and can be deleted in bulk.
Attack History
Menu: Attack History
You view the history of DDoS attacks made against your IPs.
| Column | Description |
|---|---|
| Target IP | Target of the attack |
| Reason | Attack type (e.g. volumetric attack) |
| Detail | Attack detail (e.g. UDP flood, TCP SYN flood) |
| Peak BPS | Highest bits/second value |
| Peak PPS | Highest packets/second value |
| Start | Time the attack started |
| End | Time the attack ended (empty if ongoing) |
Filtering
- Date Range: Select a start and end date to view attacks in a specific period
- IP Filter: Filter attacks made against a specific IP address
Attack data is automatically updated every 5 minutes.
Abuse Filtered
Menu: Abuse Filtered
You view your IPs that have been filtered on the Path.net side due to abuse.
- Filtered IPs are listed in a table (search and pagination)
- The current list is pulled from Path.net using the "Synchronize" button
- By opening the history from an IP's row you can see when it entered and left the filter
Panel User Guide
Menu: Panel User Guide
This is the page where you view guide content specially prepared for you, organized into categories, about how to use the panel's features.
Changing Password
- Click the profile icon in the left menu
- Select the "Change Password" option
- Enter your current password (required)
- Enter your new password and confirm it
- Click the "Save" button
API Access (Optional)
If API access has been enabled by the Admin, additional pages appear in the left menu.
API Settings
- API Key: Create your API key by clicking the "Generate Key" button (the full key is shown, blurred spoiler)
- IP Whitelist: Add IP addresses to allow access to the API only from specific IP addresses
- API Logs: View the history of requests made to the API (search, sort, pagination)
- Rate Limit: The maximum number of requests you can make per minute
API Documentation
With endpoint details, a response codes table and the "Try" feature you can test directly. The endpoints you can use:
| Endpoint | Method | Description |
|---|---|---|
/external/health | GET | API connection check |
/external/ips | GET | IP list |
/external/rules | GET | All rules in the user + their hierarchy |
/external/rules/count | GET | Total rule count (hierarchical) |
/external/rules/count/ip/:address | GET | Single IP rule count |
/external/rules/count/ip/:address/:prefix | GET | CIDR/subnet rule count (max /20) |
/external/rules/ip/:address | GET | Rules belonging to a single IP |
/external/rules/ip/:address/:prefix | GET | CIDR block rules (max /20, aligned to network address) |
/external/rules | POST | Create a new rule |
/external/rules/:id | DELETE | Delete a rule |
/external/filters | GET | Filter list |
/external/attack-history | GET | Attack history |
Authentication
For all API requests you must send your key with the X-API-Key header:
curl -H "X-API-Key: YOUR_API_KEY" https://panel.rexe.tr/external/ips
Frequently Asked Questions
Why do My IPs appear empty?
IPs are assigned to you by your parent user (Reseller). No IP may have been assigned yet; contact your Reseller.
Why are there so few filter options?
When creating a rule, only the filters permitted to you are shown. For more filters, contact your Reseller.
A rule is stuck in the "failed" status, what should I do?
Click the retry button. If the problem persists, report it to your parent user.
Why is the attack history empty?
No attack may have been made against your IPs yet, or your IPs may not have been assigned yet.
Related Articles
Game Server DDoS Filter Selection Guide (Path.net)
Path.net DDoS protection game filters guide: Arma/DayZ, Source Engine, CS:GO, CS2, FiveM, Minecraft, Rust and more — how to apply each filter.
Application and Service DDoS Filter Guide (Path.net)
Path.net DDoS protection application filters guide: OpenVPN, Wireguard, DTLS, RTP, QUIC, SIP, TCP Symmetric and more — how to choose the right filter.
Does REXE Apply Null Route? DDoS Protection Policy
REXE Technology and Path.net null route policy: With 10Tbps+ capacity, your server stays protected regardless of attack size — no null routing ever applied.