desync-engine

Design and validate DPI desynchronization pipelines for RIPDPI across TUN and proxy modes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use when designing or reviewing DPI desync evasion chains, TcpChainStep/UdpChainStep configurations, OffsetExpr/OffsetBase expressions, fake-packet injection, TLS-prelude steps, strategy-probe candidate behavior, fake-TTL semantics across TUN vs proxy mode, or anything in the ripdpi-config/ripdpi-desync/ripdpi-desync-runtime/ripdpi-proxy-runtime desync pipeline. Triggers on "desync", "DesyncMode", "fake packet", "TTL", "OOB", "tlsrec", "QUIC initial split", or DPI-bypass strategy questions.

Core Features & Use Cases

  • Documents the three-layer desync pipeline: configuration model, planning, and execution.
  • Covers TcpChainStep/UdpChainStep variants, TLS prelude steps, OffsetExpr/OffsetBase offsets, entropy padding, fake-packet mechanics, TTL and MD5 signal controls, and runtime integration across TUN and proxy modes.
  • Provides design guidance for adding new techniques, strategy-candidate evaluation, and safety/validation considerations with integration points across ripdpi-config, ripdpi-desync, and ripdpi-runtime.

Quick Start

Design a new desync technique by editing ripdpi-config and run the planner against a test payload to generate a DesyncPlan.

Frequently Asked Questions about desync-engine

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

FAQPage Schema
How does DPI desync evasion work for bypassing network filtering?

DPI desync evasion disrupts deep packet inspection by manipulating TCP/UDP packet sequences and TLS prelude structures. It applies fake-packet injection, TTL controls, and adaptive offsets across TUN and proxy modes to bypass network filtering.

How do I design a desync pipeline using TcpChainStep and OffsetExpr configurations?

Design a desync pipeline by defining configuration models in ripdpi-config, then generate a DesyncPlan using the planner. Specify TcpChainStep or UdpChainStep variants, set OffsetExpr adaptive offsets, and validate safety checks before runtime execution.

Can I use fake TTL packets for DPI evasion in both TUN and proxy modes?

Fake TTL packets function differently across TUN and proxy modes due to varying network layer routing behaviors. The desync pipeline accommodates these fake-TTL semantics, ensuring injected packets expire correctly before reaching the target while still disrupting DPI tracking.

What is the best way to handle TLS prelude and QUIC initial splits for DPI bypass?

Handling TLS prelude and QUIC initial splits requires configuring specific desync steps that fragment the ClientHello message. The pipeline supports TLS prelude steps and entropy padding to split payloads precisely, preventing DPI engines from matching signature patterns.

How do I validate and add new desync techniques to a ripdpi runtime?

Add new desync techniques by editing ripdpi-config definitions and running the planner against test payloads. Evaluate strategy-probe candidates, verify MD5 signal controls, and ensure integration points across ripdpi-desync and ripdpi-runtime pass safety validations.

Why is my desync strategy not bypassing DPI despite using fake packet injection?

Desync strategies fail when adaptive offsets or fake-TTL values are misconfigured for the specific execution mode. Review OffsetBase expressions, verify TUN versus proxy mode semantics, and validate strategy-probe candidate behavior against actual DPI responses.