erebe/wstunnel

Tunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 31 minutes ago
Added to GitGenius on September 9th, 2026
Created on May 14th, 2016
Open Issues & Pull Requests: 26 (+0)
GitHub issues: Enabled
Number of forks: 564
Total Stargazers: 7,032 (+1)
Total Subscribers: 56 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 22
New in 7 days: 2
Closed in 7 days: 9
Avg open age: 295 days
Stale 30+ days: 18
Stale 90+ days: 13

Recent activity

Opened in 7 days: 2
Closed in 7 days: 8
Comments in 7 days: 1
Events in 7 days: 1

Top labels

  • bug (60)
  • enhancement (42)
  • help wanted (30)
  • wont-do (2)

Detailed Description

Wstunnel is a tunneling tool that routes traffic over WebSocket, HTTP2, or WebTransport protocols to bypass firewalls and DPI restrictions.

The tool addresses the problem of constrained network access behind firewalls and proxies by encapsulating traffic within HTTP-compatible protocols that are typically allowed through network equipment. It works by accepting connections on a local endpoint and forwarding them through a WebSocket or HTTP2 tunnel to a remote server, which then relays the traffic to its final destination. This approach makes the tunneled traffic appear as ordinary web traffic, helping it evade protocol-based filtering.

Wstunnel suits users who need to access resources from restricted networks, whether for legitimate remote access or circumventing network policies. It supports both static tunneling for specific services and dynamic tunneling through SOCKS5 and HTTP proxies, as well as transparent proxy mode. The tool handles TCP, UDP, and Unix socket traffic, and can itself operate behind an HTTP proxy. It includes TLS/HTTPS support with automatic certificate reloading and mutual TLS authentication. Standalone binaries are available, requiring no runtime dependencies. The README names an earlier Node.js-based project as inspiration but does not compare the current tool to other tunneling solutions.

The project maintains a substantial user base, with almost all open issues coming from outside users rather than the core team. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker centers on bug reports, enhancement requests, and decisions not to implement certain features.