Opened 9 years ago

Closed 9 years ago

Last modified 7 years ago

#1627 closed enhancement (worksforme)

Set Advertized Bandwidth

Reported by: Henfre Owned by: None yet, but hopeful
Priority: Very Low Milestone:
Component: Core Tor/Tor Version: Tor: 0.2.2.x-final
Severity: Keywords: tor relay bandwidth tor-relay
Cc: Actual Points:
Parent ID: #4381 Points:
Reviewer: Sponsor:

Description

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.

Child Tickets

Change History (9)

comment:1 Changed 9 years ago by Henfre

Priority: normaltrivial
Resolution: duplicate
Status: newclosed

comment:2 Changed 9 years ago by Henfre

Oops, submitted twice. See #1626

comment:3 Changed 9 years ago by nickm

Resolution: duplicate
Status: closedreopened

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

comment:4 Changed 9 years ago by 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.)

comment:5 in reply to:  4 Changed 9 years ago by Henfre

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.

comment:6 Changed 9 years ago by nickm

Resolution: worksforme
Status: reopenedclosed

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

comment:7 Changed 8 years ago by karsten

Milestone: Tor Check Enhancements
Parent ID: #4381

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

comment:8 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:9 Changed 7 years ago by nickm

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