Opened 3 years ago

Last modified 11 months ago

#21358 new defect

Tor fails to reconnect after computer resumes from sleep

Reported by: weasel Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.9.8
Severity: Normal Keywords: sleep, wakeup, power-management, online-detection, tor-client, sponsor8-maybe, 033-triage-20180320, 033-removed-20180320
Cc: fdsfgs@… Actual Points:
Parent ID: Points: 5
Reviewer: Sponsor:

Description

A user reports that tor 0.2.9.x does not work after resumes, similar (or the same as) bug #19969, marked already fixed.

https://bugs.debian.org/853146:

Tor (or tor with little t) doesn't reconnect automatically to Tor
network after I resume my computer from sleep. So instead I have to
run "sudo systemctl restart tor" to get it working again. Though, I
think it reconnects automatically after several minutes of computer
being on but I would like it to reconnect immediately after the
computer has resumed from sleep.

I'm not sure if tor uses systemd but so if it uses maybe there is some
'resume sleep' hook in systemd that could be used for tor to
reconnect. Please let me know if you think such change would cause
some other problems.

Child Tickets

Change History (12)

comment:1 Changed 3 years ago by dgoulet

Milestone: Tor: 0.3.1.x-final

comment:2 Changed 3 years ago by yawning

As far as I can tell this is a separate issue from #19969. "tor never reconnecting" is fixed. This bug is "it reconnects automatically after several minutes" when the behavior maybe should be "reconnect immediately".

I suppose one option here is to make tor network interface aware, so it knows to do the right thing when the interface gets torn down/brought back up by the suspend.

One workaround that's semi-automated would be something like using NetworkManager's dispatcher functionality (see NetworkManager(8)).

comment:3 Changed 3 years ago by tokotoko

Cc: fdsfgs@… added

comment:4 Changed 3 years ago by nickm

Points: 5

comment:5 Changed 3 years ago by nickm

Keywords: triaged-out-20170308 added
Milestone: Tor: 0.3.1.x-finalTor: unspecified

Deferring all 0.3.1 tickets with status == new, owner == nobody, sponsor == nobody, points > 0.5, and priority < high.

I'd still take patches for most of these -- there's just nobody currently lined up to work on them in this timeframe.

comment:6 Changed 2 years ago by nickm

Keywords: sleep wakeup power-management online-detection tor-client sponsor8-maybe added; triaged-out-20170308 removed

comment:7 Changed 2 years ago by nickm

Milestone: Tor: unspecifiedTor: 0.3.2.x-final
Sponsor: Sponsor8-can

comment:8 Changed 2 years ago by nickm

Milestone: Tor: 0.3.2.x-finalTor: 0.3.3.x-final

comment:9 Changed 21 months ago by nickm

Keywords: 033-triage-20180320 added

Marking all tickets reached by current round of 033 triage.

comment:10 Changed 21 months ago by nickm

Keywords: 033-removed-20180320 added

Mark all not-already-included tickets as pending review for removal from 0.3.3 milestone.

comment:11 Changed 21 months ago by nickm

Milestone: Tor: 0.3.3.x-finalTor: unspecified

These tickets were marked as removed, and nobody has said that they can fix them. Let's remember to look at 033-removed-20180320 as we re-evaluate our triage process, to see whether we're triaging out unnecessarily, and to evaluate whether we're deferring anything unnecessarily. But for now, we can't do these: we need to fix the 033-must stuff now.

comment:12 Changed 11 months ago by gaba

Sponsor: Sponsor8-can
Note: See TracTickets for help on using tickets.