Skip to main content

wow-client

PyPI - Version PyPI - Python Version

English | 中文

The client for the WoW VPN project (https://github.com/zaf-x/WoW). Connects to the server over TLS, authenticates with a 128-bit token, sets up a local TUN device and routes traffic through the tunnel. A live status panel shows transfer rates and client↔server / client↔internet latency.

Requires Linux and root (TUN device + raw ICMP socket for the latency probe).

Usage

# connect directly (trust a custom CA with -c ca.pem)
sudo wow-client start -s vpn.example.com -p 9999 -t <32-hex-chars>

# save servers as named profiles, then pick one interactively
sudo wow-client save myserver -s vpn.example.com -p 9999 -t <32-hex-chars>
sudo wow-client launch

If sudo reports wow-client: command not found, the binary lives outside sudo's PATH (e.g. a pipx or --user install in ~/.local/bin) — run sudo "$(which wow-client)" ... instead.

Options

Subcommand Flag Description
start, save -s, --host <host> VPN server hostname or address (required)
-p, --port <n> VPN server port (required)
-t, --token <hex> 128-bit authentication token, 32 hex chars (required)
-c, --ca-cert <file> PEM CA certificate to trust for verifying the server (default: system CA bundle)
--mtu <n> TUN device MTU (default: 1200 — fits the server's NAT egress path; raise only when the egress is known larger)
--no-panel Disable the live status panel (useful for debugging, keeps logs visible)
save name Profile name to save the server under (positional argument)
launch — Pick a saved profile interactively and connect

Profiles

Profiles are stored in $XDG_CONFIG_HOME/wow-client/config.json (~/.config/wow-client/config.json by default), readable only by the owner:

{
  "profiles": {
    "myserver": {
      "host": "vpn.example.com",
      "port": 443,
      "token": "<32-hex-chars>",
      "ca_cert": null,
      "mtu": 1200
    }
  }
}

ca_cert may be a path to a PEM CA certificate, or null to use the system default CA bundle. mtu is the TUN device MTU (default 1200). The file can also be edited by hand.

Install

pip install .

License

wow-client is distributed under the terms of the MIT license.

Metadata

Release files for wow-client 1.3.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for wow-client 1.3.2
File Size Uploaded
wow_client-1.3.2.tar.gz 14.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for wow-client 1.3.2
File Interpreter ABI Platform
wow_client-1.3.2-py3-none-any.whl Python 3 none any Details

Total release size: 29.2 kB

Release files / wow_client-1.3.2.tar.gz

Download URL wow_client-1.3.2.tar.gz
Size 14.3 kB
Tags Source
SHA-256 checksum
How to use checksums
cc07af50208243e4ef78a5a8967e33c9969951a6f2334de90daaffda9b869846
BLAKE2b-256 checksum
How to use checksums
b06ae12c444602fa0782f158a343548be60996842a06c7cf5f0a16a4e8d26c0e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.4

Release files / wow_client-1.3.2-py3-none-any.whl

Download URL wow_client-1.3.2-py3-none-any.whl
Size 14.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ef4f149dab66d08f376cdd4edb5777094e247b419a784736912b9c89d05d3230
BLAKE2b-256 checksum
How to use checksums
a446223904b39aa1501bd895dbbb5b52f32c35e5cc1d6f17f3668b8eedd0aadf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.4

Release history Release notifications | RSS feed

1.3.3

2 release files

This release

1.3.2 This release

2 release files

1.3.1

2 release files

1.3.0

2 release files

1.2.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page