ws-tunnel-telegram

Configure a Telegram MTProto WS tunnel in RIPDPI with rustls or BoringSSL backends.

58|4|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/po4yka/RIPDPI --skill ws-tunnel-telegram
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ws-tunnel-telegram
Source: https://github.com/po4yka/RIPDPI/tree/main/.claude/skills/ws-tunnel-telegram
Command: npx skills add https://github.com/po4yka/RIPDPI --skill ws-tunnel-telegram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Telegram MTProto traffic is subject to DPI-based blocking; this Skill provides a structured approach to modify the MTProto WebSocket tunnel in ripdpi-ws-tunnel, enabling domain and DC-aware routing, TLS handshake reliability, and diagnostics to improve reach and stability.

Core Features & Use Cases

  • WS tunnel configuration for Telegram MTProto, including TLS backend selection (rustls or BoringSSL) and MTProto obfuscated2 handling.
  • Telegram DC routing support and MTProto seed classification to map to appropriate WS endpoints, with encrypted DNS bootstrap for DoH/DoT resilience.
  • Diagnostics integration (telegram_availability) to monitor ws tunnel health and report RTT, errors, and quality scores in telemetry.

Quick Start

Configure ripdpi-ws-tunnel to route Telegram MTProto traffic through the WS tunnel and run telegram_availability tests to verify connectivity.

Frequently Asked Questions about ws-tunnel-telegram

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route Telegram MTProto traffic over a WebSocket tunnel to bypass DPI blocking?

To route Telegram MTProto over a WebSocket tunnel, you must encapsulate MTProto in WebSocket over TLS. This approach modifies the WS tunnel to support domain and DC-aware routing, evading DPI detection while maintaining stable Telegram connectivity.

Why does my Telegram MTProto WebSocket tunnel fail TLS handshakes under DPI inspection?

MTProto WS tunnels fail TLS handshakes when they trigger DPI invariants like the blocked 517-byte ClientHello. Selecting a robust TLS backend like rustls or BoringSSL and applying MTProto obfuscated2 handling resolves these handshake failures.

How do I configure domain and DC-aware routing for a Telegram MTProto WS tunnel?

Configuring DC-aware routing for a Telegram MTProto WS tunnel requires mapping MTProto seed classifications to appropriate WS endpoints. This ensures traffic reaches the correct Telegram data centers while utilizing encrypted DNS bootstrap for DoH and DoT resilience.

Can I use BoringSSL or rustls for the TLS backend in a Telegram MTProto WS tunnel?

Yes, you can configure the MTProto WebSocket tunnel with either rustls or BoringSSL TLS backends. Choosing between these backends allows you to optimize TLS handshake reliability and meet specific cryptographic requirements for DPI evasion.

What is the best way to monitor WebSocket tunnel health and connectivity for Telegram MTProto?

The best way to monitor WS tunnel health is by running telegram_availability diagnostic probes. These probes measure tunnel connectivity, reporting RTT, errors, and quality scores in telemetry to verify stable MTProto routing.

Do I need encrypted DNS bootstrap to operate a Telegram MTProto WS tunnel?

Yes, encrypted DNS bootstrap is required to operate a reliable MTProto WS tunnel. It provides DoH and DoT resilience, ensuring that DNS queries for Telegram DC endpoints are resolved securely without interception or blocking.