Skip to content

feat: add Slipstream Plus transport support#81

Open
FarmehrF wants to merge 3 commits intonet2share:mainfrom
FarmehrF:feature/slipstream-plus
Open

feat: add Slipstream Plus transport support#81
FarmehrF wants to merge 3 commits intonet2share:mainfrom
FarmehrF:feature/slipstream-plus

Conversation

@FarmehrF
Copy link
Copy Markdown
Contributor

@FarmehrF FarmehrF commented Apr 1, 2026

Add Slipstream Plus transport support

This adds Slipstream Rust Plus (Fox-Fig/slipstream-rust-plus) as a new transport option in dnstm, alongside the existing Slipstream from net2share/slipstream-rust-build.

What is Slipstream Plus?

A performance-oriented fork of Slipstream with Turbo mode, advanced backpressure handling, and additional server configuration options. Plus has been tested and proven stable in production environments with improved throughput over standard Slipstream.

Changes

  • New transport type: slipstream-plus (separate from regular slipstream due to protocol incompatibility)
  • Config: Added SlipstreamPlusConfig with Plus-specific fields: max_connections (default 256), idle_timeout_seconds (default 60), fallback, reset_seed
  • Binary management: Downloads from Fox-Fig/slipstream-rust-deploy releases; supports Linux amd64/arm64
  • Builder: Standalone and SIP003 Shadowsocks modes with Plus-specific flags
  • TUI/CLI: "Slipstream Plus" option in interactive menu; non-interactive --transport slipstream-plus
  • Handlers: Cert generation (reuses existing TLS infrastructure), status display, config load validation
  • Tests: Integration tests for config/defaults/validation; serialization round-trip confirmed

Compatibility

  • Plus clients only work with Plus servers (protocol differences from standard Slipstream)
  • All existing backends supported (SOCKS, SSH, Shadowsocks, Custom)
  • Existing Slipstream tunnels unaffected; users explicitly choose Plus at creation time

Testing

  • All unit and integration tests pass (go test ./internal/... ./tests/integration/...)
  • Production deployments have validated stability and performance improvements

FarmehrF and others added 3 commits April 1, 2026 18:17
Remove duplicate old implementation that was incorrectly merged.
The main branch refactored to use binman wrappers, but conflict
resolution kept both old switch-based and new wrapper implementations.

Made-with: Cursor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant