#24769: Increase client idle and connection timeouts to reduce network load
-------------------------------------------------+-------------------------
Reporter: teor | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone: Tor:
| 0.3.2.x-final
Component: Core Tor/Tor | Version: Tor:
| 0.3.1.1-alpha
Severity: Normal | Resolution:
Keywords: tor-client, dos-resistance, | Actual Points:
032-backport, 031-backport, 029-backport, 025 |
-backport-maybe |
Parent ID: #24716 | Points: 1
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Changes (by teor):
* keywords: tor-client, dos-resistance =>
tor-client, dos-resistance, 032-backport, 031-backport, 029-backport,
025-backport-maybe
Comment:
Replying to [comment:1 arma]:
> Woah. Yeah. So, right now we close circuits 60 seconds after making
them, even if we opt to make testing circuits much less frequently? That
is, when we have any predicted ports, we're going to end up churning
through all our circuits every minute, anyway? That's crummy. It seems
like the idle-timeout-while-learning should be a function of the
cbttestfreq?
Yes, I think we need to make it configurable, and possibly backport the
change.
(But not to 0.2.8, because it's not supported as of 1 January 2018.)
I'm not sure what to do about the regular connection timeout. We should
check what it was before, and maybe see if it needs to be longer.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24769#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
