Opened 9 years ago

Last modified 2 years ago

#2178 new defect

We launch dummy descriptor fetches more often than needed

Reported by: nickm Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.1.26
Severity: Normal Keywords: tor-relay performance IP-probe
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Right now, we have code in update_router_descriptor_downloads() to launch a fetch for authority.z if we want to learn our IP from a directory fetch. We do this if:

  • We're a server
  • We don't have the Address option set
  • At least 20 minutes have passed since we last launched a router descriptor download
  • At least 20 minutes have passed since we last launched a

Per discussion in bug #652, we could be even more quiet about launching these fetches. We could also require that

  • At least 20 minutes have passed since we last launched *any* appropriate directory op.
  • At least 20 minutes have passed since we got a new incoming connection on what we think our IP is.
  • At least 20 minutes have passed since we got confirmation of our current IP in a NETINFO cell

We could also make the "20 minutes" value configurable by a networkstatus parameter.

This is a minor issue, since the current behavior is inelegant, but not actually hurting anything.

Child Tickets

Change History (4)

comment:1 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:2 Changed 7 years ago by nickm

Component: Tor RelayTor

comment:3 Changed 2 years ago by nickm

Keywords: performance IP-probe added
Severity: Normal

comment:4 Changed 2 years ago by nickm

Also see #2628

Note: See TracTickets for help on using tickets.