Skip to content

GitLab

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

Closed
Opened by Trac@tracbot

Document MaxAdvertisedBandwidth in the bandwidth list spec

I've set MaxAdvertisedBandwidth to 100 KB (though RelayBandwidthRate and RelayBandwidthBurst are set to 128 KB and 153 KB, respectively). Accordingly, the relay does not advertise any bandwidth higher than 100 KB. However, the consensus is reporting greater bandwidth:

valid-after 2013-03-17 01:00:00 r PrivateJoker hWF85kNElIsLrCPNTiIkX39mwcg r5DGWEd9ufF4TFXJITuOhw+by6I 2013-03-16 19:18:56 107.197.196.79 443 80 s Fast Named Running Stable V2Dir Valid v Tor 0.2.4.11-alpha w Bandwidth=108 p reject 1-65535

The bandwidth line from the descriptor looks like:

bandwidth 102400 156672 155648

My understanding is that clients use the consensus bandwidth measurement to weigh which paths to choose (correct me if I'm wrong).  If this is true, then the consensus should not report bandwidth greater than MaxAdvertisedBandwidth.  Perhaps the consensus should never show bandwidth greater than a relay's chosen RelayBandwidthRate?

Trac:
Username: alphawolf

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information