Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S Snowflake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 71
    • Issues 71
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • Snowflake
  • Issues
  • #25723
Closed
Open
Created Apr 05, 2018 by David Fifield@dcfOwner

Multiplex - one client splits traffic across multiple proxies

This is the dual of legacy/trac#25601 (moved).

It would be a great feature if a client could be connected to multiple snowflake proxies at once, and split traffic across all of them. Like the Conflux proposal for Tor. It would be a hedge against getting assigned a single slow proxy.

This would require interposing some kind of sequencing and reliability layer, with possible retransmissions.

A potential benefit for privacy is that an individual snowflake proxy only sees a subset of a client's traffic flow.

However, instantly making N WebRTC connections is a tell for traffic classification.

Assignee
Assign to
Time tracking