โ† All skills
Tencent SkillHub ยท Communication & Collaboration

WireGuard

Configure WireGuard VPN tunnels with secure routing and key management.

skill openclawclawhub Free
0 Downloads
0 Stars
0 Installs
0 Score
High Signal

Configure WireGuard VPN tunnels with secure routing and key management.

โฌ‡ 0 downloads โ˜… 0 stars Unverified but indexed

Install for OpenClaw

Quick setup
  1. Download the package from Yavira.
  2. Extract the archive and review SKILL.md first.
  3. Import or place the package into your OpenClaw setup.

Requirements

Target platform
OpenClaw
Install method
Manual import
Extraction
Extract archive
Prerequisites
OpenClaw
Primary doc
SKILL.md

Package facts

Download mode
Yavira redirect
Package format
ZIP package
Source platform
Tencent SkillHub
What's included
SKILL.md

Validation

  • Use the Yavira download entry.
  • Review SKILL.md after the package is downloaded.
  • Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

  1. Download the package from Yavira.
  2. Extract it into a folder your agent can access.
  3. Paste one of the prompts below and point your agent at the extracted folder.
New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Trust & source

Release facts

Source
Tencent SkillHub
Verification
Indexed source record
Version
1.0.0

Documentation

ClawHub primary doc Primary doc: SKILL.md 7 sections Open source page

AllowedIPs Traps (Most Common Mistakes)

AllowedIPs means different things on each side โ€” server: what peer CAN send; client: what to ROUTE through tunnel 0.0.0.0/0 routes ALL traffic including tunnel endpoint โ€” breaks connectivity, must exclude server's public IP first Overlapping AllowedIPs between peers = undefined routing โ€” each IP range must belong to exactly one peer Wrong mask silently breaks routing โ€” /32 for single host, /24 for subnet, verify carefully

Connection Failures

No handshake = wrong public key, firewall blocking UDP, or wrong endpoint โ€” check all three, not just one One-way traffic = AllowedIPs misconfigured โ€” packets go out but replies don't route back Missing PersistentKeepalive = 25 breaks NAT traversal โ€” peer behind NAT unreachable after ~2 minutes Config file permissions must be 600 โ€” wg-quick silently refuses to start with loose permissions

DNS Leaks

Without DNS = in client config, DNS queries bypass tunnel โ€” leaks real IP to DNS provider Full tunnel (0.0.0.0/0) without DNS config = false sense of security โ€” traffic tunneled but DNS exposed

Routing Setup

IP forwarding disabled by default on Linux โ€” tunnel works but packets don't route between interfaces NAT required for internet access through tunnel โ€” without masquerade, return packets don't find their way Firewall must allow UDP on ListenPort โ€” WireGuard is UDP only, no TCP fallback exists

Key Security

Private key file permissions matter โ€” world-readable key is compromised, set 600 immediately after generation Never transmit private keys โ€” generate on each machine, exchange only public keys Config files contain private keys โ€” treat wg0.conf as secret, not just privatekey file

Live Changes

Adding peers requires interface reload on most setups โ€” or use wg set for live changes without dropping connections wg syncconf applies changes without restart โ€” but config file format differs from wg.conf (use wg-quick strip)

Debugging

wg show displays handshake timestamps โ€” stale handshake (>2 min) means connection dead despite interface up Handshake happens on first packet โ€” no traffic = no handshake attempt, ping to test

Category context

Messaging, meetings, inboxes, CRM, and teammate communication surfaces.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package
1 Docs
  • SKILL.md Primary doc