菜单
Create and manage TCP/UDP tunnels between ZTM network endpoints. Use this to establish secure P2P port forwarding through the ZTM mesh network.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/johnalbertini14-glitch/openclaw-skills --skill ztm-tunnel命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | ztm-tunnel |
| description | Create and manage TCP/UDP tunnels between ZTM network endpoints. Use this to establish secure P2P port forwarding through the ZTM mesh network. |
| metadata | {"openclaw":{"emoji":"🔌","requires":{"bins":["ztm"],"services":["ztm-agent"]},"install":[{"id":"download","kind":"download","label":"Download ZTM from GitHub releases","url":"https://github.com/flomesh-io/ztm/releases"}],"env":{"ZTM_AGENT":"http://localhost:7777"},"config":{"path":"~/.ztm.conf","fields":{"agent":"ZTM Agent URL (default: localhost:7777)","mesh":"Default mesh name"}}}} |
Create and manage TCP/UDP tunnels between ZTM network endpoints.
ZTM Agent must be running
ztm start agent
Join a mesh network
ztm join <mesh-name> --as <your-endpoint-name> --permit <permit-file.json>
Tunnel app must be installed
ztm app install tunnel
List all tunnels in the mesh:
ztm tunnel get tunnel
List inbound tunnels (local listening ports):
ztm tunnel get inbound
List outbound tunnels (remote targets):
ztm tunnel get outbound
Step 1: On the remote endpoint (outbound), specify target services:
ztm tunnel open outbound my-tunnel --targets 192.168.1.100:8080
Step 2: On the local endpoint (inbound), set up port forwarding:
ztm tunnel open inbound my-tunnel --listen 0.0.0.0:9000 --exits <remote-endpoint-id>
This creates a tunnel where:
9000 listens for connections192.168.1.100:8080Create both ends at once by running on respective endpoints:
# On endpoint A (listening side)
ztm tunnel open inbound tunnel-name --listen 0.0.0.0:9000 --exits <endpoint-B-id>
# On endpoint B (target side)
ztm tunnel open outbound tunnel-name --targets 127.0.0.1:8080
Close the inbound end:
ztm tunnel close inbound my-tunnel
Close the outbound end:
ztm tunnel close outbound my-tunnel
View detailed tunnel information:
ztm tunnel describe tunnel tcp/my-tunnel
View inbound details:
ztm tunnel describe inbound tcp/my-tunnel
View outbound details:
ztm tunnel describe outbound tcp/my-tunnel
# On home endpoint
ztm tunnel open inbound home-server --listen 0.0.0.0:22 --exits <office-endpoint-id>
# On office endpoint
ztm tunnel open outbound home-server --targets 192.168.1.10:22
# Remote endpoint exposes local web service
ztm tunnel open outbound web-tunnel --targets 192.168.1.100:80
# Local endpoint listens on port 8080
ztm tunnel open inbound web-tunnel --listen 0.0.0.0:8080 --exits <remote-endpoint-id>
ztm tunnel open outbound dns-tunnel --targets 8.8.8.8:53
ztm tunnel open inbound dns-tunnel --listen 0.0.0.0:5300 --exits <remote-endpoint-id>
Check if ZTM agent is running:
curl http://localhost:7777/api/status
Check mesh status:
ztm get mesh
ztm get ep
Check installed apps:
ztm get app
If tunnel app is not installed:
ztm app install tunnel
View tunnel app logs:
ztm log app tunnel
ZTM CLI config is stored in ~/.ztm.conf:
{
"agent": "localhost:7777",
"mesh": "my-mesh-name"
}
Or set via environment:
export ZTM_AGENT=http://localhost:7777
export ZTM_MESH=my-mesh-name
For programmatic access, use the ZTM Agent HTTP API:
# Get all tunnels
curl http://localhost:7777/api/meshes/{mesh}/apps/ztm/tunnel/api/tunnel
# Get inbound tunnels
curl http://localhost:7777/api/meshes/{mesh}/apps/ztm/tunnel/api/inbound
# Create inbound
curl -X POST http://localhost:7777/api/meshes/{mesh}/apps/ztm/tunnel/api/inbound/tcp/tunnel-name \
-H "Content-Type: application/json" \
-d '{"listens":[{"ip":"0.0.0.0","port":9000}],"exits":["endpoint-id"]}'