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
  • #24557

Closed (moved)
(moved)
Open
Created Dec 08, 2017 by teor@teor

Add a "NoIPv6Consensus" flag to consensus-health

If a relay has different ReachableIPv6 addresses, and there is a tie for the most common ReachableIPv6 address, the authorities won't add any IPv6 ORPort in the consensus.

We could label the consensus column as NoIPv6Consensus in this case, instead of leaving it blank.

If this does start happening more, it would be great to know about it. And it would also help relay operators in this situation.

(See the discussion on the metrics list.)

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