Opened 2 years ago

Last modified 20 months ago

#22663 new defect

Tor keeps using a very slow guard

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.3.0.8
Severity: Normal Keywords: tor-guard, tor-client, api, performance, 032-unreached
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I'm running Tor Browser 7.0.1 with tor 0.3.0.8.

My guard slowed down significantly in the past week.
It became very hard to get pages to load completely, although sometimes partial data was returned.

I expect that after a lot of failures to connect to an exit (there are hundreds in my logs) tor would at least try another guard.

But it didn't, and there is no easy way for me to tell it to try another guard. (New Circuit only changes middle and exit, the state file isn't reloaded on HUP #22662, and I didn't try New Identity, but NEWNYM is not documented to reset guards).

Maybe making it hard to change guards is a feature, but if it is, we need to either use more than 1 guard (linkability implications), or give up on a slow guard.

Child Tickets

Change History (4)

comment:1 Changed 2 years ago by cypherpunks

Give up on a slow guard, pick a new guard, then revert back to the previous guard if it becomes fast (i.e. the Fast relay flag) again?

FWIW I experienced this same issue when I was using some obfs4 bridges last year, unfortunately I don't think there can be anything done to address this issue with bridges at least currently.

Last edited 2 years ago by cypherpunks (previous) (diff)

comment:2 in reply to:  1 Changed 2 years ago by teor

Replying to cypherpunks:

Give up on a slow guard, pick a new guard, then revert back to the previous guard if it becomes fast (i.e. the Fast relay flag) again?

FWIW I experienced this same issue when I was using some obfs4 bridges last year, unfortunately I don't think there can be anything done to address this issue with bridges at least currently.

The guard dropped to 670kBps reported bandwidth, but measures at 4000 and observes itself at 6MBps. So it didn't lose the Fast flag as far as I can tell.

comment:3 Changed 22 months ago by nickm

Keywords: tor-guard tor-client api performance added
Milestone: Tor: 0.3.1.x-finalTor: 0.3.2.x-final

comment:4 Changed 20 months ago by nickm

Keywords: 032-unreached added
Milestone: Tor: 0.3.2.x-finalTor: unspecified

Mark a large number of tickets that I do not think we will do for 0.3.2.

Note: See TracTickets for help on using tickets.