Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S Snowflake WebExtension
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • 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 WebExtension
  • Issues
  • #20
Closed
Open
Created Jan 20, 2021 by Cecylia Bocovich@cohoshOwner

Change NAT check to increase time between checks and prevent proxies from reverting to unknown

Something went wrong with how we are doing the probetest and our counts of unrestricted proxies dropped from 77 to almost zero overnight. I don't know the cause, but I'd like to propose the following change in how we handle NAT checks:

  • proxies will only perform the check on startup or once a week
  • unrestricted proxies that have too many failures will trigger a check
  • if a proxy had a concrete NAT type (restricted or unrestricted) before the check, and the check comes back inconclusive (unknown), keep the old NAT type.
Assignee
Assign to
Time tracking