Set Advertized Bandwidth

If it is true that tor uses other tor nodes to measure our bandwidth it is possible that we may connect to comparatively slow servers if we are on a very fast connection. This would cause us to under-report and so under-utilize available bandwidth.

Used properly this would allow server owners to better exploit faster connections when bandwidth is notably and surely under-reported.

Trac:
Username: Henfre

added bandwidth component::core tor/tor owner::None yet owner::but hopeful parent::4381 priority::very low relay reporter::Henfre resolution::worksforme status::closed tor tor-relay type::enhancement version::tor 0.2.2.x-final labels

Trac:
Username: Henfre
Resolution: N/A to duplicate
Status: new to closed
Priority: normal to trivial

Oops, submitted twice. See #1626 (moved)

Trac:
Username: Henfre

Servers' self-advertised bandwidth is no longer used to decide how much to use them: it's too easy for a malicious server to

Trac:
Resolution: duplicate to N/A
Status: closed to reopened

Oops; closed the other one before I saw that you closed this one.

Anyway: Servers' self-advertised bandwidth is no longer the main factor used to decide how much to use them: it's too easy for a malicious server to lie and claim more bandwidth than it has. Instead, clients now base their decision on measured bandwidth as estimated by one or more 'bandwidth authorities'. See proposals 160 and 161 for an intro to the topic.

(Also, it's not the individual connection to any other server that a Tor process uses to estimate its own bandwidth. Instead, it uses the maximum aggregate bandwidth that it has ever been able to push out in a given time period over all connections.)

Replying to nickm:

Oops; closed the other one before I saw that you closed this one.

Anyway: Servers' self-advertised bandwidth is no longer the main factor used to decide how much to use them: it's too easy for a malicious server to lie and claim more bandwidth than it has. Instead, clients now base their decision on measured bandwidth as estimated by one or more 'bandwidth authorities'. See proposals 160 and 161 for an intro to the topic.

(Also, it's not the individual connection to any other server that a Tor process uses to estimate its own bandwidth. Instead, it uses the maximum aggregate bandwidth that it has ever been able to push out in a given time period over all connections.)

Ahh, I understand. In any case I have convinced myself that my ISP throttles encrypted traffic significantly compared to browsing and download over http. This is what prevents my node from using all of the seemingly available bandwidth. Thank you for the rapid response.

Trac:
Username: Henfre

closing as not-a-bug: self-advertised bandwidth doesn't work as feared.

Trac:
Status: reopened to closed
Resolution: N/A to worksforme

Assigning as a child ticket to the project ticket that replaces the "Tor Check Enhancements" milestone.

Trac:
Points: N/A to N/A
Actualpoints: N/A to N/A
Parent: N/A to #4381 (moved)
Milestone: Tor Check Enhancements to N/A

Trac:
Keywords: tor, relay, bandwidth deleted, tor relay bandwidth tor-relay added

Trac:
Component: Tor Relay to Tor

closed

moved to tpo/core/tor#1627 (closed)