aboutsummaryrefslogtreecommitdiff
path: root/src/or/or.h
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2013-02-14 11:48:47 -0500
committerNick Mathewson <nickm@torproject.org>2013-02-14 11:48:47 -0500
commit91027218e29090b18d42e1868367cc2a9e149900 (patch)
tree715e210ba876dbe45f564207c31816e8cf389a65 /src/or/or.h
parent47cfee781d104a23ed44318c0c763c9834c0b7b6 (diff)
downloadtor-91027218e29090b18d42e1868367cc2a9e149900.tar
tor-91027218e29090b18d42e1868367cc2a9e149900.tar.gz
Add some code to bluntly prevent duplicate guards from getting added
Apparently something in the directory guard code made it possible for the same node to get added as a guard over and over when there were no actual running guard nodes.
Diffstat (limited to 'src/or/or.h')
-rw-r--r--src/or/or.h3
1 files changed, 3 insertions, 0 deletions
diff --git a/src/or/or.h b/src/or/or.h
index 04640d050..df69674d3 100644
--- a/src/or/or.h
+++ b/src/or/or.h
@@ -2233,6 +2233,9 @@ typedef struct node_t {
/** Local info: we treat this node as if it rejects everything */
unsigned int rejects_all:1;
+ /** Local info: this node is in our list of guards */
+ unsigned int using_as_guard:1;
+
/* Local info: derived. */
/** True if the IPv6 OR port is preferred over the IPv4 OR port. */