aboutsummaryrefslogtreecommitdiff
path: root/src/app/config/or_options_st.h
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2021-03-17 08:45:37 -0400
committerNick Mathewson <nickm@torproject.org>2021-03-17 08:45:37 -0400
commit2ae24d003d1d12e8e202748c4398d7438e4a65d9 (patch)
treeed28225754a655c069a9a6d5fd6b66af2fdfc205 /src/app/config/or_options_st.h
parent59bbf8cde9144ee5c8d060959e723a4bedfd6bb8 (diff)
downloadtor-2ae24d003d1d12e8e202748c4398d7438e4a65d9.tar.gz
tor-2ae24d003d1d12e8e202748c4398d7438e4a65d9.zip
Add a MinTimeToReportBandwidth option; make it 0 for testing networks.
This option changes the time for which a bandwidth measurement period must have been in progress before we include it when reporting our observed bandwidth in our descriptors. Without this option, we only consider a time period towards our maximum if it has been running for a full day. Obviously, that's unacceptable for testing networks, where we'd like to get results as soon as possible. For non-testing networks, I've put a (somewhat arbitrary) 2-hour minimum on the option, since there are traffic analysis concerns with immediate reporting here. Closes #40337.
Diffstat (limited to 'src/app/config/or_options_st.h')
-rw-r--r--src/app/config/or_options_st.h4
1 files changed, 4 insertions, 0 deletions
diff --git a/src/app/config/or_options_st.h b/src/app/config/or_options_st.h
index 4364f145ed..efecc85d66 100644
--- a/src/app/config/or_options_st.h
+++ b/src/app/config/or_options_st.h
@@ -1082,6 +1082,10 @@ struct or_options_t {
/** List of policy allowed to query the Metrics port. */
struct config_line_t *MetricsPortPolicy;
+ /** How far must we be into the current bandwidth-measurement period to
+ * report bandwidth observations from this period? */
+ int MinTimeToReportBandwidth;
+
/**
* Configuration objects for individual modules.
*