EasyTier

https://easytier.cn/guide/
Admin
EasyTier is a decentralized VPN networking tool that enables peer-to-peer connections with features...
Tokens:28,779
Snippets:377
Trust Score:7.3
Update:3 months ago
Show doc for...
Tokens:
Raw
### Manage EasyTier Service: Start (Windows)

Source: https://easytier.cn/guide/network/oneclick-install-as-service.html

Starts the installed EasyTier system service on Windows.

```powershell
.
easytier-cli.exe service start
```

--------------------------------

### Manage EasyTier Service: Start (Linux)

Source: https://easytier.cn/guide/network/oneclick-install-as-service.html

Starts the installed EasyTier system service on Linux.

```shell
sudo ./easytier-cli service start
```

--------------------------------

### Download and Run install.cmd

Source: https://easytier.cn/guide/network/install-as-a-windows-service.html

Use this command to download the `install.cmd` script and execute it to install EasyTier. It will guide you through the configuration.

```powershell
iwr "https://raw.githubusercontent.com/EasyTier/EasyTier/main/script/install.cmd" -OutFile "install.cmd"; .\install.cmd
```

--------------------------------

### Install and Enable Fail2ban

Source: https://easytier.cn/guide/network/host-public-server.html

Install fail2ban using dnf and enable it to start automatically on boot.

```shell
# install fail2ban
sudo dnf install fail2ban

# enable and start
sudo systemctl enable --now fail2ban
```

--------------------------------

### Full Configuration File Example

Source: https://easytier.cn/guide/network/secure-mode.html

An example of a complete EasyTier configuration file, including settings for credential persistence, network identity, and secure mode.

```toml
credential_file = "/var/lib/easytier/credentials.json"

[network_identity]
network_name = "office"
network_secret = "replace-with-a-strong-secret"

[secure_mode]
enabled = true
local_private_key = "<optional-base64-private-key>"
```

--------------------------------

### Install EasyTier as a Service (Windows)

Source: https://easytier.cn/guide/network/oneclick-install-as-service.html

Installs EasyTier as a system service on Windows. Requires easytier-core and easytier-cli in the same directory. The arguments after 'install' are passed to easytier-core.

```powershell
.
easytier-cli.exe service install -w abc
```

--------------------------------

### Install EasyTier Service

Source: https://easytier.cn/guide/network/install-as-a-windows-service.html

Execute the `install.cmd` script to install the EasyTier service. Follow the prompts to select a configuration mode and provide necessary parameters.

```powershell
.\install.cmd
```

--------------------------------

### Install EasyTier as a Service (Linux)

Source: https://easytier.cn/guide/network/oneclick-install-as-service.html

Installs EasyTier as a system service on Linux. Requires easytier-core and easytier-cli in the same directory. The arguments after 'install' are passed to easytier-core.

```shell
sudo ./easytier-cli service install -w abc
```

--------------------------------

### One-Click Installation Script for Linux

Source: https://easytier.cn/guide/installation.html

This bash script automates the installation of EasyTier on Linux systems. It downloads the script, installs the program, and registers it as a system service.

```bash
wget -O /tmp/easytier.sh "https://raw.githubusercontent.com/EasyTier/EasyTier/main/script/install.sh" && sudo bash /tmp/easytier.sh install --gh-proxy https://ghfast.top/
```

--------------------------------

### Run EasyTier with a Configuration File

Source: https://easytier.cn/guide/network/config-file.html

Specify the path to your configuration file using the -c parameter. This example uses a YAML configuration file.

```sh
easytier-core -c ./config.yaml
```

--------------------------------

### Verify EasyTier Installation (Windows)

Source: https://easytier.cn/guide/installation.html

After manually downloading and extracting the EasyTier command-line program, use this command to verify the installation on Windows.

```powershell
.\easytier-core.exe --version
```

--------------------------------

### Verify EasyTier Installation (Linux/macOS)

Source: https://easytier.cn/guide/installation.html

After manually downloading and extracting the EasyTier command-line program, use this command to verify the installation on Linux, macOS, or FreeBSD.

```bash
./easytier-core --version
```

--------------------------------

### Manage EasyTier System Service (Linux)

Source: https://easytier.cn/guide/installation.html

After installation using the one-click script on Linux, EasyTier is registered as a system service. Use this command to start the service with the default configuration.

```bash
systemctl start easytier@default
```

--------------------------------

### Advanced Service Installation with Options (Linux)

Source: https://easytier.cn/guide/network/oneclick-install-as-service.html

Installs EasyTier as a service on Linux with custom descriptions, display names, autostart settings, and paths. The '--' separates options from easytier-core arguments.

```shell
sudo ./easytier-cli service install \
    --description "自定义服务描述" \
    --display-name "显示名称" \
    --disable-autostart \
    --core-path /path/to/easytier-core \
    --service-work-dir /工作目录路径 \
    -- -w abc
```

--------------------------------

### Advanced Service Installation with Options (Windows)

Source: https://easytier.cn/guide/network/oneclick-install-as-service.html

Installs EasyTier as a service on Windows with custom descriptions, display names, autostart settings, and paths. The '--' separates options from easytier-core arguments.

```powershell
.
easytier-cli.exe service install `
    --description "自定义服务描述" `
    --display-name "显示名称" `
    --disable-autostart `
    --core-path /path/to/easytier-core `
    --service-work-dir /工作目录路径 `
    -- -w abc
```

--------------------------------

### Start EasyTier Service

Source: https://easytier.cn/guide/network/install-as-a-macos-service.html

Commands to start the EasyTier service and load its launchd task. The `-w` option ensures the task restarts on login or reboot.

```bash
sudo launchctl start easytier
launchctl load -w /Library/LaunchDaemons/easytier.plist
```

--------------------------------

### Enable EasyTier Systemd Service

Source: https://easytier.cn/guide/network/install-as-a-systemd-service.html

Enable the EasyTier service to start automatically on system boot.

```bash
systemctl enable easytier.service
```

--------------------------------

### Run EasyTier with a TOML Configuration File

Source: https://easytier.cn/guide/network/config-file.html

Load a configuration file using the -c parameter. This example demonstrates using a TOML configuration file, which can be generated using the EasyTier Configuration Assistant.

```sh
easytier-core -c ./config.toml
```

--------------------------------

### Install EasyTier from Source using Cargo

Source: https://easytier.cn/guide/installation.html

Install EasyTier directly from its Git repository using the Cargo package manager. This method requires a Rust environment and LLVM.

```sh
cargo install --git https://github.com/EasyTier/EasyTier.git easytier
```

--------------------------------

### Run EasyTier as a Public Server

Source: https://easytier.cn/guide/network/host-public-server.html

Start EasyTier without any parameters to make the node a public server. This requires no root privileges.

```shell
easytier-core
```

--------------------------------

### Start EasyTier with Subnet Proxy

Source: https://easytier.cn/guide/network/point-to-networking.html

Start EasyTier with the `-n` parameter to specify the subnet that this node will proxy. This allows other nodes in the virtual network to access the specified subnet.

```bash
sudo easytier-core --ipv4 10.144.144.2 -n 10.1.1.0/24
```

--------------------------------

### Start and Stop EasyTier Systemd Service

Source: https://easytier.cn/guide/network/install-as-a-systemd-service.html

Commands to manually start and stop the EasyTier service.

```bash
systemctl start easytier.service
systemctl stop easytier.service
```

--------------------------------

### Run EasyTier with Multiple Configuration Files

Source: https://easytier.cn/guide/network/config-file.html

You can specify multiple configuration files using the -c parameter. EasyTier will load all specified files and start multiple virtual networks within a single process.

```sh
easytier-core -c ./config1.yaml -c ./config2.yaml
```

--------------------------------

### Run EasyTier Core on Node A (Windows)

Source: https://easytier.cn/guide/network/quick-networking.html

Use this command to start EasyTier on Node A. Ensure you run it with administrator privileges. The `-d` flag enables automatic virtual IP assignment.

```powershell
# 管理员权限运行
.
ieasytier-core.exe -d --network-name abc --network-secret abc -p tcp://<共享节点 IP或域名>:1010
```

--------------------------------

### Start EasyTier with Manual Routes

Source: https://easytier.cn/guide/network/point-to-networking.html

Use the `--manual-routes` parameter to manually configure which network segments should be forwarded to the virtual network. If the list is empty, no non-virtual network traffic will be processed.

```bash
sudo easytier-core --ipv4 10.144.144.2 -n 10.1.1.0/24 --manual-routes 10.1.1.0/24
```

--------------------------------

### Install Fish Shell Autocompletion for EasyTier

Source: https://easytier.cn/guide/installation.html

This command generates and installs shell autocompletion for EasyTier's core and CLI components in the Fish shell. Ensure the output file path is correct for your Fish configuration.

```fish
# Fish 补全
easytier-core --gen-autocomplete fish > ~/.config/fish/completions/easytier-core.fish
easytier-cli gen-autocomplete fish > ~/.config/fish/completions/easytier-core.fish
```

--------------------------------

### Run EasyTier Core on Node A (Linux)

Source: https://easytier.cn/guide/network/quick-networking.html

Use this command to start EasyTier on Node A. Ensure you run it with administrator privileges. The `-d` flag enables automatic virtual IP assignment.

```sh
# 管理员权限运行
./easytier-core -d --network-name abc --network-secret abc -p tcp://<共享节点 IP或域名>:1010
```

--------------------------------

### Start a Node in a Two-Node Network

Source: https://easytier.cn/guide/network/decentralized-networking.html

Run this command on the first node to initiate a virtual network. It specifies the virtual network IP address. The node will listen on default ports for various protocols.

```bash
sudo easytier-core -i 10.144.144.1
```

--------------------------------

### Start Management Node with Credential Persistence

Source: https://easytier.cn/guide/network/secure-mode.html

Start the management node with secure mode enabled and configure a credential file for persistent storage of issued credentials. This ensures that issued credentials remain valid across node restarts.

```sh
easytier-core -d \
  --network-name office \
  --network-secret 'replace-with-a-strong-secret' \
  --secure-mode \
  --credential-file /var/lib/easytier/credentials.json \
  -p tcp://node-a.example.com:11010
```

--------------------------------

### Obtain WireGuard Client Configuration

Source: https://easytier.cn/guide/network/use-easytier-with-wireguard-client.html

After `easytier-core` starts successfully, use the `easytier-cli vpn-portal` command to retrieve the WireGuard client configuration. This output includes the necessary interface and peer details for the client.

```sh
$> easytier-cli vpn-portal
portal_name: wireguard

client_config:
[Interface]
PrivateKey = 9VDvlaIC9XHUvRuE06hD2CEDrtGF+0lDthgr9SZfIho=
Address = 10.14.14.0/24 # should assign an ip from this cidr manually

[Peer]
PublicKey = zhrZQg4QdPZs8CajT3r4fmzcNsWpBL9ImQCUsnlXyGM=
AllowedIPs = 192.168.80.0/20,10.147.223.0/24,10.144.144.0/24
Endpoint = 0.0.0.0:11013 # should be the public ip of the easytier server

connected_clients: []

```

--------------------------------

### Open Internet (IPv4) Connectivity Example

Source: https://easytier.cn/guide/aboutp2p.html

Illustrates direct inbound connections to a public IP address without NAT. This is common for public IPs with no firewall restrictions.

```text
120.120.120.120:25565 ← 111.111.111.111:x（x代表任意端口）
120.120.120.120:25565 ← 222.222.222.222:x（x代表任意端口）
120.120.120.120:25565 ← 333.333.333.333:x（x代表任意端口）
120.120.120.120:25565 ← 444.444.444.444:x（x代表任意端口）
```

--------------------------------

### No Pat NAT (IPv4) Connectivity Example

Source: https://easytier.cn/guide/aboutp2p.html

Demonstrates Basic NAT where only the IP address is translated, and the port remains the same. This is common in home or small office networks.

```text
192.168.1.1:25565 ← 120.120.120.120:25565 ← 111.111.111.111:x（x代表任意端口）
192.168.1.1:25565 ← 120.120.120.120:25565 ← 222.222.222.222:x（x代表任意端口）
192.168.1.1:25565 ← 120.120.120.120:25565 ← 333.333.333.333:x（x代表任意端口）
192.168.1.1:25565 ← 120.120.120.120:25565 ← 444.444.444.444:x（x代表任意端口）
```

--------------------------------

### Open Internet (IPv6) Connectivity Example

Source: https://easytier.cn/guide/aboutp2p.html

Demonstrates direct inbound connections to a public IPv6 address without NAT. Similar to IPv4, this applies to public IPv6 addresses without firewall restrictions.

```text
[240e:3fd8:256a:3367::1]:25565 ← [240e::1]:x（x代表任意端口）
[240e:3fd8:256a:3367::1]:25565 ← [240e::2]:x（x代表任意端口）
[240e:3fd8:256a:3367::1]:25565 ← [240e::3]:x（x代表任意端口）
[240e:3fd8:256a:3367::1]:25565 ← [240e::4]:x（x代表任意端口）
```

--------------------------------

### EasyTier UDP Performance Test (No Encryption)

Source: https://easytier.cn/guide/perf.html

Starts EasyTier core in UDP mode without encryption on the 'red' namespace and initiates a UDP test from the 'green' namespace using iperf3.

```bash
ip netns exec red easytier-core -i 10.126.126.2 --multi-thread -u
ip netns exec green easytier-core -i 10.126.126.3 -p udp://192.168.0.2:11010 --multi-thread -u
ip netns exec green iperf3 -c 10.126.126.2
```

--------------------------------

### Symmetric Firewall (IPv6) Connectivity Example

Source: https://easytier.cn/guide/aboutp2p.html

Illustrates connections to a public IPv6 address behind a firewall. Inbound traffic is filtered, requiring specific firewall rules for direct connections.

```text
[240e:3fd8:256a:3367::1]:25565 ↚ [240e::1]:x（x代表任意端口）
[240e:3fd8:256a:3367::1]:25565 ↚ [240e::2]:x（x代表任意端口）
[240e:3fd8:256a:3367::1]:25565 ↚ [240e::3]:x（x代表任意端口）
[240e:3fd8:256a:3367::1]:25565 ↚ [240e::4]:x（x代表任意端口）
```

--------------------------------

### Symmetric Firewall (IPv4) Connectivity Example

Source: https://easytier.cn/guide/aboutp2p.html

Shows connections to a public IP behind a firewall that filters inbound traffic. Direct connections are blocked unless the firewall policy allows them.

```text
120.120.120.120:25565 ↚ 111.111.111.111:x（x代表任意端口）
120.120.120.120:25565 ↚ 222.222.222.222:x（x代表任意端口）
120.120.120.120:25565 ↚ 333.333.333.333:x（x代表任意端口）
120.120.120.120:25565 ↚ 444.444.444.444:x（x代表任意端口）
```

--------------------------------

### Full Cone NAT (IPv6) Connectivity Example

Source: https://easytier.cn/guide/aboutp2p.html

Demonstrates Full Cone NAT for IPv6, translating both IP and port. This allows any external host to connect to the translated public port, mapping to the internal IPv6 address and port.

```text
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:35565 ← [240e::1]:x（x代表任意端口）
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:35565 ← [240e::2]:x（x代表任意端口）
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:35565 ← [240e::3]:x（x代表任意端口）
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:35565 ← [240e::4]:x（x代表任意端口）
```

--------------------------------

### Configure EasyTier Node as WireGuard Server

Source: https://easytier.cn/guide/network/use-easytier-with-wireguard-client.html

Add the `--vpn-portal` parameter to the `easytier-core` command to specify the WireGuard service port and network segment. This example configures it to listen on port 11013 and use the 10.14.14.0/24 network for WireGuard.

```sh
sudo easytier-core --ipv4 10.144.144.1 --vpn-portal wg://0.0.0.0:11013/10.14.14.0/24
```

--------------------------------

### Enable KCP Proxy

Source: https://easytier.cn/guide/network/kcp-proxy.html

Enable KCP proxy functionality on a node by specifying the `--enable-kcp-proxy` flag when starting EasyTier. The proxy automatically falls back to TCP if the peer does not support KCP.

```sh
sudo easytier-core --enable-kcp-proxy
```

--------------------------------

### View KCP Proxy Connection Status

Source: https://easytier.cn/guide/network/kcp-proxy.html

Use the `easytier-cli proxy` command to view all active connections, including their source, destination, start time, state, and transport type (e.g., Tcp, Kcp).

```bash
$ easytier-cli proxy

┌────────────────────┬───────────────────┬─────────────────────────┬───────────┬────────────────┐
│ src                │ dst               │ start_time              │ state     │ transport_type │
├────────────────────┼───────────────────┼─────────────────────────┼───────────┼────────────────┤
│ 10.126.126.7:51838 │ 10.147.223.128:22 │ 2025-02-07 10:39:08 UTC │ Connected │ Tcp            │
├────────────────────┼───────────────────┼─────────────────────────┼───────────┼────────────────┤
│ 0.0.0.0:0          │ 10.147.223.1:80   │ 2025-02-07 10:41:28 UTC │ Connected │ Kcp            │
├────────────────────┼───────────────────┼─────────────────────────┼───────────┼────────────────┤
│ 0.0.0.0:0          │ 10.147.223.1:80   │ 2025-02-07 10:41:18 UTC │ Connected │ Kcp            │
└────────────────────┴───────────────────┴─────────────────────────┴───────────┴────────────────┘
```

--------------------------------

### Full Cone NAT (IPv4) Connectivity Example

Source: https://easytier.cn/guide/aboutp2p.html

Illustrates Full Cone NAT where both IP address and port are translated. Any external host can connect to the translated public port, which maps to the internal IP and port.

```text
192.168.1.1:25565 ← 120.120.120.120:35565 ← 111.111.111.111:x（x代表任意端口）
192.168.1.1:25565 ← 120.120.120.120:35565 ← 222.222.222.222:x（x代表任意端口）
192.168.1.1:25565 ← 120.120.120.120:35565 ← 333.333.333.333:x（x代表任意端口）
192.168.1.1:25565 ← 120.120.120.120:35565 ← 444.444.444.444:x（x代表任意端口）
```

--------------------------------

### Symmetric Easy Increase NAT (IPv6) Connectivity Example

Source: https://easytier.cn/guide/aboutp2p.html

Illustrates Symmetric Easy Increase NAT for IPv6, featuring patterned port mappings with restrictions on inbound IP and port. The mapped ports follow a systematic progression.

```text
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:35565 ← [240e::1]:11010
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:35567 ← [240e::2]:22020
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:35569 ↚ [240e::1]:33030
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:35571 ↚ [240e::3]:x（x代表任意端口）
```

--------------------------------

### Create EasyTier Systemd Service File

Source: https://easytier.cn/guide/network/install-as-a-systemd-service.html

Define the systemd service for EasyTier. Modify `ExecStart` with your specific command-line arguments.

```systemd
[Unit]
Description=EasyTier Service
After=network.target syslog.target
Wants=network.target

[Service]
Type=simple
ExecStart=/root/easytier-core --ipv4 x.x.x.x --network-name xxx --network-secret yyy --peers tcp://peer_host:11010

[Install]
WantedBy=multi-user.target
```

--------------------------------

### Download and Run install.cmd with GitHub Proxy

Source: https://easytier.cn/guide/network/install-as-a-windows-service.html

If direct GitHub access is blocked, use this command with a mirror proxy to download and run the `install.cmd` script.

```powershell
iwr "https://ghfast.top/https://raw.githubusercontent.com/EasyTier/EasyTier/main/script/install.cmd" -OutFile "install.cmd"; .\install.cmd -ughp
```

--------------------------------

### Register EasyTier Service with Configuration File

Source: https://easytier.cn/guide/network/install-as-a-macos-service.html

Use this command to register the EasyTier service with a configuration file. Ensure the configuration file path is correct.

```bash
sudo serviceman add --name easytier --daemon \
--workdir /var/log/easytier \
--group wheel --user root \
-- easytier-core -c ~/.config/easytier.toml
```

--------------------------------

### Initialize Network Environment for Testing

Source: https://easytier.cn/guide/perf.html

Sets up network namespaces, bridges, and IP configurations required for performance testing. Ensures IP forwarding and bridge netfilter are configured.

```bash
apt update
apt install iperf3 iptables -y

ip netns add red
ip netns add green
ip link add br0 type bridge
ip link set br0 up
ip addr add 192.168.0.1/16 dev br0

ip link add vethcab0 type veth peer name red0
ip link set vethcab0 master br0
ip link set red0 netns red
ip netns exec red ip link set lo up
ip netns exec red ip link set red0 up
ip netns exec red ip addr add 192.168.0.2/16 dev red0
ip netns exec red ip route add default via 192.168.0.1
ip link set vethcab0 up

ip link add vethcab1 type veth peer name green0
ip link set vethcab1 master br0
ip link set green0 netns green
ip netns exec green ip link set lo up
ip netns exec green ip link set green0 up
ip netns exec green ip addr add 192.168.0.3/16 dev green0
ip netns exec green ip route add default via 192.168.0.1
ip link set vethcab1 up

sysctl net.ipv4.ip_forward=1
sysctl net.bridge.bridge-nf-call-iptables=0
sysctl net.bridge.bridge-nf-call-ip6tables=0
sysctl net.ipv6.conf.lo.disable_ipv6=0

# 注： EasyTier 不依赖公网服务，可以不配置 iptables 转发
iptables -t nat -A POSTROUTING -j MASQUERADE
iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -o eth0 -j MASQUERADE
iptables -A FORWARD -i eht0 -j ACCEPT
iptables --policy FORWARD ACCEPT

nohup ip netns exec red iperf3 -s &
```

--------------------------------

### Integrating EasyTier Core with Self-Built Web Console

Source: https://easytier.cn/guide/network/web-console.html

This command integrates the EasyTier core with a self-built web console. Replace `<protocol>`, `<host>`, `<port>`, and `<username>` with your specific configuration details. The protocol can be udp, tcp, ws, or wss.

```shell
# ./easytier-core -w <protocol>://<host>:<port>/<你在自建web控制台上的用户名>
# protocol: udp, tcp, ws, wss
./easytier-core -w udp://127.0.0.1:22020/<你在自建web控制台上的用户名>
```

--------------------------------

### Remove Extended Attributes on macOS

Source: https://easytier.cn/guide/gui/index.html

After installing the easytier-gui application on macOS, run this command in the terminal to prevent the system from incorrectly flagging the file as corrupted.

```bash
xattr -c /Applications/easytier-gui.app
```

--------------------------------

### Enable Private Mode for EasyTier

Source: https://easytier.cn/guide/network/host-public-server.html

Start EasyTier in private mode to restrict connections to nodes within the same virtual network. Specify the network name and secret.

```shell
sudo easytier-core --private-mode true --network-name my-network --network-secret my-secret
```

--------------------------------

### Configure IPv6 Listening Addresses

Source: https://easytier.cn/guide/network/p2p-optimize.html

Manually configure EasyTier to listen only on IPv6 addresses. This example shows listening on all IPv6 interfaces for both TCP and UDP protocols on port 12345.

```sh
easytier-core -l 'tcp://[::]:12345' -l 'udp://[::]:12345'

```

--------------------------------

### Deploying easytier-web-embed

Source: https://easytier.cn/guide/network/web-console.html

This command deploys the `easytier-web-embed` with specified ports and protocols for the API backend and configuration server. Ensure the ports and host are correctly configured for your environment.

```shell
./easytier-web-embed \
    --api-server-port 11211 \
    --api-host "http://127.0.0.1:11211" \
    --config-server-port 22020 \
    --config-server-protocol udp
```

--------------------------------

### Configure Relay Network Whitelist

Source: https://easytier.cn/guide/network/host-public-server.html

Limit which virtual networks can be relayed by this node. An empty list disables relaying for all other networks. This example also enables relaying only RPC traffic.

```shell
easytier-core --relay-network-whitelist --relay-all-peer-rpc
```

--------------------------------

### Enable QUIC Proxy

Source: https://easytier.cn/guide/network/kcp-proxy.html

Enable QUIC proxy support by using the `--enable-quic-proxy` flag. QUIC offers higher bandwidth in high-loss environments compared to KCP.

```sh
sudo easytier-core --enable-quic-proxy
```

--------------------------------

### Register EasyTier Service without Configuration File

Source: https://easytier.cn/guide/network/install-as-a-macos-service.html

Use this command to register the EasyTier service without a configuration file, specifying network parameters directly. Replace placeholders with actual values.

```bash
sudo serviceman add --name easytier --daemon \
--workdir /var/log/easytier \
--group wheel --user root \
-- easytier-core --ipv4 x.x.x.x --network-name xxx --network-secret yyy --peers tcp://peer_host:11010
```

--------------------------------

### Run LoopBack Test with iperf3

Source: https://easytier.cn/guide/perf.html

Executes an iperf3 client command within the 'green' network namespace to test LoopBack device performance.

```bash
ip netns exec green iperf3 -c 192.168.0.2
```

--------------------------------

### Enable KCP Proxy with User-Space Network Stack

Source: https://easytier.cn/guide/network/kcp-proxy.html

Combine `--enable-kcp-proxy` with `--use-smoltcp` to utilize a user-space network stack, which can resolve issues caused by system firewalls when using the default kernel network stack.

```sh
sudo easytier-core --enable-kcp-proxy --use-smoltcp
```

--------------------------------

### Load TUN Driver and Create TUN Device on Linux

Source: https://easytier.cn/guide/faq.html

Load the TUN driver using 'modprobe tun'. If the /dev/net/tun device does not exist, create it using 'mkdir -p /dev/net' and 'sudo mknod /dev/net/tun c 10 200'. This is necessary for network tunneling functionalities.

```bash
modprobe tun
mkdir -p /dev/net
sudo mknod /dev/net/tun c 10 200
```

--------------------------------

### Configure P2P Connection Behavior with Flags

Source: https://easytier.cn/guide/network/p2p-optimize.html

Use these flags to control how EasyTier nodes establish P2P connections. `--lazy-p2p` delays P2P establishment until traffic is needed, `--need-p2p` prioritizes incoming P2P connections, and `--disable-p2p` stops automatic P2P attempts. Combine `--disable-p2p` with `--need-p2p` for a whitelist approach.

```bash
--lazy-p2p

```

```bash
--need-p2p

```

```bash
--disable-p2p

```

```bash
--disable-p2p --need-p2p

```

--------------------------------

### No Pat NAT (IPv6) Connectivity Example

Source: https://easytier.cn/guide/aboutp2p.html

Shows Basic NAT for IPv6, where the IP address is translated but the port remains consistent. This type of NAT preserves the original port for internal communication.

```text
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:25565 ← [240e::1]:x（x代表任意端口）
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:25565 ← [240e::2]:x（x代表任意端口）
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:25565 ← [240e::3]:x（x代表任意端口）
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:25565 ← [240e::4]:x（x代表任意端口）
```

--------------------------------

### Restricted Cone NAT (IPv4) Connectivity Example

Source: https://easytier.cn/guide/aboutp2p.html

Shows Restricted Cone NAT where inbound connections are limited to specific external IP addresses. Only specified IPs can connect to the translated public port.

```text
192.168.1.1:25565 ← 120.120.120.120:35565 ← 111.111.111.111:x（x代表任意端口）
192.168.1.1:25565 ← 120.120.120.120:35565 ↚ 222.222.222.222:x（x代表任意端口）
192.168.1.1:25565 ← 120.120.120.120:35565 ↚ 333.333.333.333:x（x代表任意端口）
192.168.1.1:25565 ← 120.120.120.120:35565 ↚ 444.444.444.444:x（x代表任意端口）
```

--------------------------------

### Competitor Tool UDP Test (With Encryption)

Source: https://easytier.cn/guide/perf.html

Configures a competitor tool ('xxx') for UDP testing with encryption in the 'red' namespace and runs an iperf3 client in the 'green' namespace.

```bash
ip netns exec red xxx -k iperf -s 8.134.146.7:29872 -w 1234 --ip 10.26.0.2
ip netns exec green xxx -k iperf -s 8.134.146.7:29872 -w 1234 --ip 10.26.0.3
ip netns exec green iperf3 -c 10.26.0.2
```

--------------------------------

### View EasyTier Service Logs

Source: https://easytier.cn/guide/network/install-as-a-macos-service.html

Command to view the real-time logs of the EasyTier service. Use `tail -f` to follow the log output.

```bash
sudo tail -f /var/log/easytier.log
```

--------------------------------

### Restricted Cone NAT (IPv6) Connectivity Example

Source: https://easytier.cn/guide/aboutp2p.html

Illustrates Restricted Cone NAT for IPv6, limiting inbound connections to specific external IPv6 addresses. Only the designated IPs can connect to the translated public port.

```text
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:35565 ← [240e::1]:x（x代表任意端口）
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:35565 ↚ [240e::2]:x（x代表任意端口）
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:35565 ↚ [240e::3]:x（x代表任意端口）
[fd00::1]:25565 ← [240e:3fd8:256a:3367::1]:35565 ↚ [240e::4]:x（x代表任意端口）
```

--------------------------------

### EasyTier Systemd Service Unit File

Source: https://easytier.cn/guide/network/host-public-server.html

A sample systemd service unit file for EasyTier, including configuration for hostname, network, secret, and file descriptor limits.

```shell
# cat /etc/systemd/system/easytier.service

[Unit]
Description=EasyTier Service
After=network.target syslog.target
Wants=network.target

[Service]
Type=simple
ExecStart=/usr/local/bin/easytier-core --hostname <your-hostname> --network-name <your-network> --network-secret <your-secret> 
Restart=always
RestartSec=3
LimitNOFILE=1048576
Environment=TOKIO_CONSOLE=1

[Install]
WantedBy=multi-user.target
```

--------------------------------

### Symmetric Easy Increase NAT (IPv4) Connectivity Example

Source: https://easytier.cn/guide/aboutp2p.html

Shows Symmetric Easy Increase NAT where mappings have a predictable pattern. This type has restrictions on both IP and port for inbound connections, with a systematic increase in mapped ports.

```text
192.168.1.1:25565 ← 120.120.120.120:35565 ← 111.111.111.111:11010
192.168.1.1:25565 ← 120.120.120.120:35566 ← 222.222.222.222:22020
192.168.1.1:25565 ← 120.120.120.120:35567 ↚ 111.111.111.111:33030
192.168.1.1:25565 ← 120.120.120.120:35568 ↚ 333.333.333.333:x（x代表任意端口）
```
Tokens:
Raw