Warp Native

Cloudflare Warp Native is a way to use the Cloudflare Warp service over WireGuard in native mode: a direct WireGuard setup with no dependency on the official Cloudflare client (the 1.1.1.1 app or warp-cli). In wgcf terms, it means a generated WireGuard profile connected to the Cloudflare Warp infrastructure, usable in any WireGuard-compatible client.

The module builds on two open-source projects:

WARP Native

Install and uninstall scripts: bring WARP up on the node server as a regular WireGuard interface.

Modenative, no Cloudflare clientTrafficonly the selected domainsVerificationchecksums from two sources

distillium@distillium

↗ warp-native

wgcf

The profile generator: creates a free WARP account and turns it into a ready WireGuard config.

Rolethe WARP profile for the interfaceAccountcreated automaticallyFormata standard WireGuard config

ViRb3@ViRb3

↗ wgcf

What is Cloudflare Warp?

Cloudflare Warp is a service that routes user traffic through Cloudflare servers, providing:

• Security: traffic encryption to protect the data.
• Privacy: hiding the user’s IP address.
• Optimization: routing through Cloudflare’s global network for better speed and reliability.

How it works

From the panel server the module adds the warp-out outbound and a routing rule with the selected domains to the node’s configuration profile. The node sends only those domains through the warp interface, everything else goes direct, and websites see a Cloudflare address instead of the server’s own.

The module menu

The WARP Native by distillium item in the script’s main menu opens four actions:

root@server: ~

WARP Native
 Details in the wiki: https://wiki.egam.es/configuration/warp-native

1.Install WARP Native
2.Uninstall WARP Native

3.Add WARP-configuration to node configuration
4.Remove WARP-configuration from node configuration

0.Exit

Select action (0-4):

If there is no node on the server, the install starts with the red warning “Node RemnaWave not found. First install the node.”.

Installing WARP Native

Important

WARP Native is installed only on a server that runs a RemnaWave node.

1. Select Install WARP Native

   root@server: ~

   WARP Native
    Details in the wiki: https://wiki.egam.es/configuration/warp-native
   
   1.Install WARP Native
   2.Uninstall WARP Native
   
   3.Add WARP-configuration to node configuration
   4.Remove WARP-configuration from node configuration
   
   0.Exit
   
   Select action (0-4):

2. The script downloads and runs the wgcf installer: before running, it is verified against checksums from two independent sources; on a mismatch the run is cancelled.

Adding WARP settings

Important

Run only on the server with the RemnaWave panel installed.

1. Select Add WARP-configuration to node configuration and confirm you are on the panel server:

   root@server: ~

   WARP Native
   
   3.Add WARP-configuration to node configuration
   
   Are you sure you are on the server with the installed panel?
   Adding WARP-configuration should only be done on the server where the panel is installed, not on the node server
   (y/n): y

2. Then pick which node gets the WARP settings:

   root@server: ~

   Select node to add WARP-configuration?
   
   1.Default-Profile (de-fra-01)
   2.StealConfig (nl-ams-02)
   
   Select action:

3. The module adds the blocks to the node’s configuration profile and answers:

   root@server: ~

   Configuration successfully updated!

If WARP is already configured, the module warns: “warp-out already exists in outbounds.” Nothing is duplicated.

The following blocks are added to your node’s configuration profile section:

outbound

{
  "tag": "warp-out",
  "protocol": "freedom",
  "settings": {
    "domainStrategy": "UseIP"
  },
  "streamSettings": {
    "sockopt": {
      "interface": "warp",
      "tcpFastOpen": true
    }
  }
}

The highlighted domains will be sent through WARP; replace them with your own.

routing rule

{
  "type": "field",
  "domain": [
    "whoer.net",
    "browserleaks.com",
    "2ip.io",
    "2ip.ru"
  ],
  "outboundTag": "warp-out"
}

Removing WARP settings

The Remove WARP-configuration from node configuration item asks for the same node and takes the additions out:

root@server: ~

Select node to remove WARP-configuration?

1.Default-Profile (de-fra-01)

Select action:

Removed warp-out from outbounds
Removed warp rule from routing rules

If the profile has no blocks left, the module says so directly: “warp-out not found in outbounds”. The WireGuard interface itself is removed by the Uninstall WARP Native item, after which the module answers “WARP deleted successfully”.