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

Closed (moved)
(moved)
Open
Created Nov 26, 2017 by Trac@tracbot

No warning when IPv6 port is not reachable

Case: Running relay on IPv4. All checks ok, running good. Stop relay, add ORPort for IPv6. Restart. Checks look ok, circuits are built up. After a while, no new users are added, but circuits disappear and relay is reported as off line in atlas. This lasted for over a day.

Reason: IPv6 port was blocked by firewall. This was not reported in the error logs (but was tested, hence the relay being reported offline). Unblock IPv6 port places the relay 'online' again, and all works well.

Request: report on IPv6 port not reachable. This would have saved quite some time and searching. Question/discussion: should a relay go offline when IPv4 works, but only IPv6 has problems? And what happens if IPv4 is taken off completely?

Trac:
Username: MikeEU

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