summaryrefslogtreecommitdiff
path: root/src/or/or.h
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2011-11-16 20:55:33 -0500
committerRoger Dingledine <arma@torproject.org>2011-11-21 18:22:10 -0500
commitc0ec4eafc54d84089536caf51b1367e8d9ddacef (patch)
tree2b487a5b8ba33bb66e0b9ded5561e47028ed70db /src/or/or.h
parentf4e053d6dff0b868449a8c225c2062b42083733f (diff)
downloadtor-c0ec4eafc54d84089536caf51b1367e8d9ddacef.tar.gz
tor-c0ec4eafc54d84089536caf51b1367e8d9ddacef.zip
parameterize bw cutoffs to guarantee Fast and Guard flags
Now it will be easier for researchers to simulate Tor networks with different values. Resolves ticket 4484.
Diffstat (limited to 'src/or/or.h')
-rw-r--r--src/or/or.h8
1 files changed, 8 insertions, 0 deletions
diff --git a/src/or/or.h b/src/or/or.h
index 7d50e1f505..c0714ee4c6 100644
--- a/src/or/or.h
+++ b/src/or/or.h
@@ -2676,6 +2676,14 @@ typedef struct {
* exploitation of CVE-2011-2768 against their clients? */
int GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays;
+ /** If non-zero, always vote the Fast flag for any relay advertising
+ * this amount of capacity or more. */
+ uint64_t AuthDirFastGuarantee;
+
+ /** If non-zero, this advertised capacity or more is always sufficient
+ * to satisfy the bandwidth requirement for the Guard flag. */
+ uint64_t AuthDirGuardBWGuarantee;
+
char *AccountingStart; /**< How long is the accounting interval, and when
* does it start? */
uint64_t AccountingMax; /**< How many bytes do we allow per accounting