Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • 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
  • Network Health
  • sbws
  • Issues
  • #40136
Closed
Open
Created May 12, 2022 by juga@jugaMaintainer

When the relay to measure is an exit, check `bwscanner_cc` and `FlowCtrl` before using it as an exit

Working on analysis#36 (closed) made me realize that we still had the line https://gitlab.torproject.org/tpo/network-health/sbws/-/blob/m15/sbws/core/scanner.py#L401 that use the relay to measure as an exit without checking bwscanner_cc or FlowCtrl, even if we added 037dd9c3.

That was causing that sometimes a CC circuit was built when bwscanner_cc wasn't equal or greater than 1 or the other way around.

Assignee
Assign to
Time tracking