Skip to content
GitLab
Projects Groups Topics 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
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 93
    • Issues 93
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • 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
  • #40178
Closed
Open
Issue created Sep 25, 2022 by Cecylia Bocovich@cohoshOwner

Handle unknown client NAT type better to reduce load on restricted proxy pool

We're seeing a large number of clientpolls with unknown NAT types:

image

To be safe, we treat unknown client NATs the same as restricted client NATs, so they pull from the smaller pool of proxies that are known to work with symmetrics NATs. It's possible we can relieve at least some of the pressure on this proxy pool by having unknown clients first try proxies from the unrestricted pool and then fall back to the restricted pool if there is a failure to connect.

Assignee
Assign to
Time tracking