Opened 15 years ago

Last modified 8 years ago

#200 closed enhancement (Implemented)

Path selection algorithm wastes exit bandwidth by choosing exits as relay nodes.

Reported by: goodell Owned by:
Priority: Low Milestone: 0.1.2.x-final
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: goodell Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Nodes with more liberal exit policies should be chosen less frequently
than nodes with more conservative exit policies, since they will
naturally attract a disproportionate number of streams exiting to that
port. For example, the fact that many streams traverse one
particular node because it provides exit to port 6881 should not
result in a concomitant bandwidth report that makes it more attractive
to clients interested in exiting to port 80.

Ideally, we would (a) take into account that two hops of each circuit
are chosen irrespectively of exit policy, and (b) we want to avoid
"popular" nodes, where "popular" is some function of the scarcity of
the ports to which they allow passage.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (3)

comment:1 Changed 15 years ago by nickm

Geoff -- are you working on this?

comment:2 Changed 14 years ago by nickm

flyspray2trac: bug closed.
A first-pass solution has been implemented in r8571. It only looks at the Exit flag, but it plays some fancy games to work on networks where (say) 70% of the nodes are Exit.

comment:3 Changed 8 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.