Opened 4 years ago

Last modified 23 months ago

#14763 new defect

Stochastic Guard Flag

Reported by: anon Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.7
Severity: Normal Keywords: guard, flag, tor-dirauth, needs-investigation
Cc: Actual Points:
Parent ID: Points: medium/large
Reviewer: Sponsor:

Description

Stochastic Guard Flag symptom and the subsequent interruption of optimal contribution to the network.

Tracking issue with some relays in family randomly losing Guard in consensus, and experiencing other low bandwidth situations sporadically.

# Not affected (always Guard once Guard):

  • Mozilla14 , 209.119.188.42_p80 , globe.torproject.org/#/relay/12259E0A607EE888B23FBFA613C2F99E32408445
  • Mozilla4 , 209.119.188.39_p443 , globe.torproject.org/#/relay/629B222746E76B1D531969187EDB9397DEC00838

# Randomish Guard loss affected:

  • Mozilla13 , 209.119.188.42_p9090 , globe.torproject.org/#/relay/95AC12EEFD2F89DBE4185E6B5B29ED0CAA5FFFE2
  • Mozilla12 , 209.119.188.41_p9090 , globe.torproject.org/#/relay/4DECCBA05C87BF208EA77C81B0BB1278B063884E
  • Mozilla11 , 209.119.188.41_p443 , globe.torproject.org/#/relay/07931503E96CBC4284EC04534D586FE63DB70992
  • Mozilla10 , 209.119.188.38_p9090 , globe.torproject.org/#/relay/BB1936B7D4F092CE83AE8590CAA07F7B56A7DF1B
  • Mozilla9 , 209.119.188.38_p443 , globe.torproject.org/#/relay/57791ADDC8A775A546A2AA8F327C1D2647990162
  • Mozilla6 , 209.119.188.40_p443 , globe.torproject.org/#/relay/9B0481C293B26E02994711046798D3D76A126F2E
  • Mozilla5 , 209.119.188.40_p9090 , globe.torproject.org/#/relay/C7E8746FE94A8318693F4EA81800149AA6A201C6
  • Mozilla2 , 209.119.188.37_p9090 , globe.torproject.org/#/relay/FD3BC0BEA5F73680E6F9F3BAC762160231DC3DB5

Note about traffic graphs when not-Guard: the middle relays appear to be handling plenty of capacity; some delta between usage in Guard or not is based on this type difference. Consider mean consensus weight fraction along with guard / middle probabilities.

Will update once consensus history is reviewed in detail for the period in question...

Child Tickets

Change History (19)

comment:1 Changed 4 years ago by anon

another report of possibly related behavior:
<martingale> can someone help me troubleshoot why my relay is so slow? been running ~30 days with one reset, i'm averaging about 3Mbps, never been above 10Mbps. I'm on a 1000Mbps connection. this was not a sudden drop when i got the guard flag. in fact, i didn't notice any change in bandwidth when i got the guard flag (since lost again). restarted only once, two days ago.

see globe.torproject.org/#/relay/18EAAF7CB6C2ABE8583841D305C06A509F8C1C82

comment:2 Changed 4 years ago by anon

specific status votes for each relay are available at freehaven.net/~arma/moria1-v3-status-votes (e.g. which auths voted Guard, Stable, Fast for relay...)

comment:3 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-final

comment:4 Changed 4 years ago by nickm

Status: newassigned

comment:5 Changed 4 years ago by nickm

Keywords: 027-triaged-1-in added

Marking more tickets as triaged-in for 0.2.7

comment:6 Changed 4 years ago by isabela

Keywords: SponsorU added
Points: medium/large
Version: Tor: 0.2.7

comment:7 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.8.x-final

comment:8 Changed 4 years ago by nickm

Keywords: SponsorU removed
Sponsor: SponsorU

Bulk-replace SponsorU keyword with SponsorU field.

comment:9 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.???

It is impossible that we will fix all 252 currently open 028 tickets before 028 releases. Time to move some out. This is my first pass through the "assigned" tickets with no owner, looking for things to move to ???.

If somebody thinks they can get these done before the 0.2.8 timeout, please assign it to yourself and move it back?

comment:10 Changed 3 years ago by isabela

Sponsor: SponsorUSponsorU-can

comment:11 Changed 3 years ago by nickm

Keywords: SponsorU-deferred added
Sponsor: SponsorU-can

Remove the SponsorU status from these items, which we already decided to defer from 0.2.9. add the SponsorU-deferred tag instead in case we ever want to remember which ones these were.

comment:12 Changed 2 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:13 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:14 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:15 Changed 2 years ago by nickm

Keywords: 027-triaged-in added

comment:16 Changed 2 years ago by nickm

Keywords: 027-triaged-in removed

comment:17 Changed 2 years ago by nickm

Keywords: 027-triaged-1-in removed

comment:18 Changed 2 years ago by nickm

Status: assignednew

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

comment:19 Changed 23 months ago by nickm

Keywords: tor-dirauth needs-investigation added; SponsorU-deferred removed
Severity: Normal
Note: See TracTickets for help on using tickets.