Opened 4 months ago

Last modified 5 weeks ago

#30477 new task

Tor should self-test reachability of TCP listeners exposed by PT's

Reported by: ahf Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: unspecified
Severity: Normal Keywords: tor-pt, network-team-roadmap-november
Cc: phw Actual Points:
Parent ID: #30471 Points:
Reviewer: Sponsor: Sponsor28-must


It would be useful if Tor would do self-test of TCP port reachability for bridge listeners and not just the ORPort itself.

Currently when a bridge operator starts their Bridge Relay, Tor will test whether their ORPort is available from the internet, but we do not test the reachability of, for example, the obfs4 TCP port.

We believe that *just* testing for whether the port is available to the internet is better than to actually test if the port, for example, is able to speak the obfs4 protocol.

We should probably have a way to disable the warning that is emitted if a port is not reachable if, for example, the bridge is actually lying to Tor about its port, does not have a port, or the port is exposed via UDP instead of TCP.

Child Tickets

Change History (4)

comment:1 Changed 4 months ago by phw

Parent ID: #30472#30471

Updating the parent to #30471 because our past parent, #30472, turned into a short-term solution that is now deployed.

comment:2 Changed 4 months ago by gaba

Keywords: ex-sponsor19 added
Sponsor: Sponsor19

Remove sponsor 19 and add a keyword ex-sponsor19 to mark all the tickets that could have been in the scope of the sponsor.

comment:3 Changed 5 weeks ago by gaba

Sponsor: Sponsor28-must

comment:4 Changed 5 weeks ago by gaba

Keywords: network-team-roadmap-november added; ex-sponsor19 removed
Note: See TracTickets for help on using tickets.