Skip to main content

​
Unified Filtering Interface

The Cosmicguard custom rule engine is an advanced management interface that allows you to architect sophisticated, stateful filters for any traffic type. By using high-level “Logic Blocks,” you can build a bespoke security perimeter that accommodates custom game modifications, proprietary applications, or unique network requirements. Unlike traditional firewalls that require separate management for different protocols, Cosmicguard provides a unified ecosystem for all network traffic.

Difficulty

Advanced

Time

10 Minutes

​
Strategic Rule Architecture

Cosmicguard uses a protocol-agnostic management style, allowing you to oversee your entire security posture from a single list.
  • Unified Management: Manage TCP, UDP, and ICMP rules in a cohesive sequence.
  • Port Flexibility: Full support for individual service ports (e.g., 25565) or expansive numeric ranges (e.g., 10000-20000) for dynamically assigned game instances.
  • Hierarchical Priority: Rules are evaluated from top to bottom. This sequence is critical when combining broad restrictions with specific exceptions.

​
Technical Logic Blocks

Rather than basic port forwarding, Cosmicguard allows you to assign specialized mitigation engines to your rules.
Logic BlockTechnical Purpose
Any TCP ApplicationGeneral stateful hardening for TCP-based services.
SynCookiesAdvanced SYN-flood protection for high-traffic environments.
Steam QueryHardened stateful validation for Valve’s A2S query protocol.
FiveM L7Deep packet inspection optimized for GTA V roleplay traffic.
Cloudflare OnlyRestricts traffic to only originated from verified Cloudflare edge nodes.
RakNet v2Protocol-specific validation for modern engines like Palworld and Rust.

​
Configuration Workflow

Follow these steps to establish a new custom filter.
1

Select Your IP

Log in to the Firewall Panel and navigate to the IP Addresses tab. Select your Cosmicguard-protected address.
2

Initialize New Rule

Open the Filtering Rules section and click Create New Rule.
3

Define Protocol & Range

Specify the protocol (TCP, UDP, or ICMP) and the destination port range you wish to safeguard.
4

Assign Mitigation Logic

Select the Logic Block that best corresponds to your application’s traffic pattern.
5

Establish Action

Set the rule action to Allow (to whitelist specific validated traffic) or Deny (to drop all matching packets).

​
Rule Sequencing

Always ensure your specific “Allow” rules for active services are positioned above any broad “Deny All” rules. If a general restriction is evaluated first, it will drop legitimate traffic before the system reaches your specific whitelist entry.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to get a new server? Use code KB20 at checkout for 20% off your first month!
Last Updated: January 2026 | Cosmicguard: Advanced network architecture.