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

Maybe try more than once if a connection timed out?

I tried to make sense of recent emma runs in Uganda (see tpo/community/outreach#40007 (closed)) and noticed that it's difficult to tell if a connection failed because of reliability issues or because of censorship. Emma currently tries once to establish a TCP connection to a target and if that fails, it labels the target as unreachable. It's up to the operating system to determine the number of TCP retransmissions. Let's teach emma to try more than once to establish a TCP connection to a target. This will increase the test time a little bit but I think the improved clarity is worth the additional wait time.

Assignee
Assign to
Time tracking