Path Panel DDoS Protection Management Panel User Guide

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 12 Tbps network capacity, this system performs stateful filtering at the L3/L4 layer, ensuring that only legitimate traffic reaches your server.

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

My IPs

Menu: My IPs

You view the IP addresses assigned to you on this page.

IP List

• 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

TR Protection Status

Each IP's Protection column shows the TR /32 protection status on the router:

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 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

Creating a New Rule

1. Click the "New Rule" button
2. 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)
3. Click the "Create" button
4. The rule is automatically sent to Path.net

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

Rule Statuses

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.

1. Click the "Ready-Made Profile" button on the rule page
2. Select a preset from the list (e.g. "Cloudflare Whitelist", "Game Server Protection")
3. All rules in the preset are applied to your IP in bulk

Attack History

Menu: Attack History

You view the history of DDoS attacks made against your IPs.

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

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

1. Click the profile icon in the left menu
2. Select the "Change Password" option
3. Enter your current password (required)
4. Enter your new password and confirm it
5. 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:

Base URL: https://x-api.rexe.tr/api/v1/external — the paths below are appended to this address.

Common error codes: 400 validation error, 401 invalid API key, 403 resource out of scope, 404 not found, 409 conflict (e.g. same IP + port), 500 server error.

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://x-api.rexe.tr/api/v1/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.