Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#24407 closed enhancement (duplicate)

No warning when IPv6 port is not reachable

Reported by: MikeEU Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version: Tor: 0.3.1.8
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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?

Child Tickets

Change History (2)

comment:1 Changed 2 years ago by Sebastian

Resolution: duplicate
Status: newclosed

See #24403 for the "do ipv6 reachability checks on relays" feature. I'm going to close this as a duplicate in favor of that other ticket. While we don't have that I argue that marking your relay non-running is the best possible course of action because it alerted you to the problem and allowed you to fix it, so today we have one more relay on IPv6 than we would've had otherwise.

comment:2 Changed 2 years ago by Sebastian

Oh, to answer your last question, every relay must have ipv4 currently. This is unlikely to change in the near future.

Note: See TracTickets for help on using tickets.