Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #32614

Closed (moved)
(moved)
Open
Created Nov 26, 2019 by David Goulet@dgoulet🆘

hs-v3: Consider flagging an intro point as bad if rendezvous fails multiple times

This comes from #25882 (moved).

Should a client claim that an IP is failing if the RP never connected? In other words, handling the CIRCUIT_PURPOSE_C_REND_READY_INTRO_ACKED purpose when cleaning up a circuit.

I would think that having a maximum amount of retries let say (arbitrarily) after 2 times that you introduce, the IP sends back the ACK but then you end up timing out the RP circuit, we would flag the IP in the failure cache and move on to a new IP.

This would not be a "catch all" issues with connectivity but would at least zone out buggy or malicious IP that do not relay the introduction.

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