Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 318
    • Issues 318
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #10993
Closed
Open
Created Feb 21, 2014 by Lunar@lunar

Fails to reconnect after connection loss when only one bridge is configured

When configured to use only a single bridge, if the connection to that bridge is lost (which typically happen when suspending or hoping from one network to another), tor will not try to reconnect even when the bridge is reachable available again.

At notice level, you can see a loop of:

smartlist_choose_node_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
compute_weighted_bandwidths(): Empty routerlist passed in to consensus weight node selection for rule weight as guard

I don't think this happen when there is more than one bridge configure but I'm not 100% sure at this time.

I also have the feeling that this did not happen with version 0.2.3, but I'm not 100% sure either.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking