[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #19984 [Core Tor/Tor]: Use a better set of comparison/evaluation functions for deciding which connections to kill when OOS
#19984: Use a better set of comparison/evaluation functions for deciding which
connections to kill when OOS
--------------------------+------------------------------------
Reporter: nickm | Owner: nickm
Type: defect | Status: accepted
Priority: High | Milestone: Tor: 0.3.3.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: dos, sockets | Actual Points:
Parent ID: | Points: 2
Reviewer: | Sponsor: SponsorV-can
--------------------------+------------------------------------
Comment (by teor):
I wonder if we should try for a load-balancing metric instead.
A recent tor-relays thread discovered that limiting the connections from
each IPv4 /16 resolves this issue:
https://lists.torproject.org/pipermail/tor-
relays/2017-December/013776.html
The equivalent IPv6 netblock would be a /32, the minimum regional internet
registry allocation block size.
We could identify the /16s or /32s with the largest numbers of
connections, and kill those first, using one of the other "usefulness"
heuristics.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19984#comment:14>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs