Overview TurkeyDPI includes four pre-configured presets optimized for different Turkish ISPs. Each preset uses specific fragmentation strategies and timing parameters to bypass DPI inspection.
Quick recommendation: Start with the aggressive preset. It works for most ISPs and situations.
Available Presets Aggressive
Türk Telekom
Vodafone TR
Superonline
Aggressive (Recommended) The most comprehensive bypass configuration. Works with all Turkish ISPs. turkeydpi bypass --preset aggressive
Technical Details: Parameter Value Description fragment_snitrueFragment TLS ClientHello SNI extension tls_split_pos0Split at SNI midpoint (dynamic) fragment_http_hosttrueFragment HTTP Host header http_split_pos1Split 1 byte into Host header send_fake_packetsfalseDon’t send decoy packets fake_packet_ttl3TTL for decoy packets (if enabled) fragment_delay_us1000010ms delay between fragments use_tcp_segmentationtrueForce TCP segmentation min_segment_size1Minimum TCP segment size max_segment_size5Maximum 5 bytes per segment
When to use:
First time using TurkeyDPI
Multiple ISPs or unknown ISP
Maximum compatibility needed
Other presets don’t work
Trade-offs:
Adds 10ms latency per fragment
More CPU usage due to small segments
Higher packet overhead
Türk Telekom Optimized for Türk Telekom’s DPI infrastructure. turkeydpi bypass --preset turk-telekom
Technical Details: Parameter Value Description fragment_snitrueFragment TLS SNI tls_split_pos2Split at byte 2 fragment_http_hosttrueFragment HTTP Host http_split_pos2Split at byte 2 send_fake_packetsfalseNo decoy packets fake_packet_ttl1fragment_delay_us0No artificial delay use_tcp_segmentationtrueTCP segmentation enabled min_segment_size1max_segment_size20Larger segments than aggressive
Why this works for TT: Türk Telekom’s DPI inspects the first few bytes of TLS records. Splitting at byte 2 breaks the record header across packets: Normal packet: [16 03 03 00 xx 01 ...] ↑ ↑ ↑ TLS handshake signature Split at 2: [16 03] | [03 00 xx 01 ...] ↑ ↑ Packet 1 Packet 2 - DPI can't classify
Advantages:
No latency penalty (0μs delay)
Lower overhead than aggressive
Tested extensively on TT network
When to use:
You’re on Türk Telekom network
You want minimal latency
Vodafone Turkey Optimized for Vodafone Turkey’s DPI systems. turkeydpi bypass --preset vodafone
Technical Details: Parameter Value Description fragment_snitrueFragment TLS SNI tls_split_pos3Split at byte 3 fragment_http_hosttrueFragment HTTP Host http_split_pos3Split at byte 3 send_fake_packetsfalseNo decoy packets fake_packet_ttl1fragment_delay_us100100μs delay (0.1ms) use_tcp_segmentationtrueTCP segmentation enabled min_segment_size1max_segment_size30Medium-sized segments
Why this works for Vodafone: Vodafone’s DPI has short-term buffering that attempts to reassemble fragments. The 100μs delay is too short for full reassembly but long enough to evade detection: [16 03 03] ──→ DPI buffer ↓ 100μs wait [00 xx 01 ...] ──→ Buffer incomplete, timeout
Advantages:
Minimal latency impact (0.1ms)
Defeats Vodafone’s buffering
Medium overhead
When to use:
You’re on Vodafone Turkey network
Balanced performance needed
Superonline Optimized for Superonline’s DPI infrastructure. turkeydpi bypass --preset superonline
Technical Details: Parameter Value Description fragment_snitrueFragment TLS SNI tls_split_pos1Split at byte 1 (very early) fragment_http_hosttrueFragment HTTP Host http_split_pos1Split at byte 1 send_fake_packetsfalseNo decoy packets fake_packet_ttl1fragment_delay_us0No delay use_tcp_segmentationtrueTCP segmentation enabled min_segment_size1max_segment_size15Smallest segments
Why this works for Superonline: Superonline’s DPI is particularly aggressive and checks record types early. Splitting at byte 1 breaks the content type detection: Normal: [16] [03 03 00 xx ...] ↑ 0x16 = TLS Handshake Split at 1: [16] | [03 03 00 xx ...] ↑ ↑ Can't identify without next bytes
Advantages:
Zero latency (no delays)
Defeats early-stage classification
Lower CPU usage than aggressive
When to use:
You’re on Superonline network
You need fast response times
How Presets Work TLS Fragmentation All presets fragment TLS ClientHello packets. The key difference is where the split occurs:
Aggressive (split_pos=0)
Turk Telekom (split_pos=2)
Vodafone (split_pos=3)
Superonline (split_pos=1)
Original: [TLS_Header][ClientHello][SNI:"discord.com"][Extensions] Fragmented: [TLS_Hea] [der][Cli] [entHell] [o][SNI:] ["discor] [d.com"] [Extensi] [ons]
HTTP Fragmentation Similarly, HTTP Host headers are fragmented:
Aggressive (split_pos=1)
Other Presets (split_pos=1-3)
GET / HTTP/1.1 Host: d|iscord.com ↑ split here
Choosing the Right Preset
Check your ISP
Find out which ISP you’re using:
Türk Telekom → use turk-telekom
Vodafone Turkey → use vodafone
Superonline → use superonline
Other/Unknown → use aggressive
Test the preset
Start TurkeyDPI with your chosen preset: turkeydpi bypass --preset < your-is p >
Verify it works
Try accessing a blocked site. If it doesn’t work:
Try the aggressive preset
Enable verbose logging: turkeydpi bypass --preset aggressive -v
Check the troubleshooting section below
Preset Comparison Preset Latency CPU Usage Compatibility Best For Aggressive High (10ms) High Universal Unknown ISP, maximum compatibility Turk Telekom None Low TT-specific Türk Telekom users Vodafone Very Low (0.1ms) Medium VF-specific Vodafone Turkey users Superonline None Low SO-specific Superonline users
Performance tip: ISP-specific presets are faster than aggressive. If you know your ISP, use its preset for better performance.
Advanced: Creating Custom Presets If the built-in presets don’t work, you can create custom configurations. See the Configuration guide for details.
Example custom config for testing: [ global ] enabled = true enable_fragmentation = true [[ rules ]] name = "custom-https" enabled = true priority = 100 transforms = [ "fragment" ] [ rules . match_criteria ] dst_ports = [ 443 ] protocols = [ "tcp" ] [ transforms . fragment ] min_size = 1 max_size = 15 # Adjust this value randomize = true
Then run:
turkeydpi run --proxy --config custom.toml
Troubleshooting Presets Preset not working
Verify the preset name: # Valid presets: turkeydpi bypass --preset aggressive turkeydpi bypass --preset turk-telekom turkeydpi bypass --preset vodafone turkeydpi bypass --preset superonline
Try aggressive preset: turkeydpi bypass --preset aggressive
Enable verbose logging: turkeydpi bypass --preset aggressive -v
Look for errors in the output.
Different ISP than expected Some users are on virtual ISPs that use another ISP’s infrastructure:
TTNet, TTNET → Use turk-telekomVodafone Red → Use vodafoneSuperbox → Use superonline
If unsure, use aggressive.
Preset causes high latency The aggressive preset adds 10ms of artificial delay. To reduce latency:
Switch to ISP-specific preset: turkeydpi bypass --preset turk-telekom # 0ms delay
Create custom config without delays:
Edit config.toml and set:[ transforms . jitter ] min_ms = 0 max_ms = 0
Next Steps
Configuration Learn how to create custom bypass configurations
Basic Usage Return to basic CLI usage guide