Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • BridgeDB BridgeDB
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • BridgeDBBridgeDB
  • Issues
  • #17007

Closed
Open
Created Sep 08, 2015 by Trac@tracbot

use dynamic ip bridges for censor prone distributors

if bridges for https and email get blocked quickly but slowly enough that they can stay online for some hours then bridges with dynamic ips could be used for that. the ip changes within one day anyway and it could even perform a reconnect to get a new ip if it detects being blocked.

this way users who obtain bridges from these ips dont get starved completely and the distributors that do not get blocked anyway it eliminates downtimes of bridges which are reconnecting.

Trac:
Username: elypter

Assignee
Assign to
Time tracking