summaryrefslogtreecommitdiff
path: root/node/Constants.hpp
diff options
context:
space:
mode:
Diffstat (limited to 'node/Constants.hpp')
-rw-r--r--node/Constants.hpp28
1 files changed, 11 insertions, 17 deletions
diff --git a/node/Constants.hpp b/node/Constants.hpp
index 67e6fb58..a625b480 100644
--- a/node/Constants.hpp
+++ b/node/Constants.hpp
@@ -180,14 +180,14 @@
#define ZT_PEER_SECRET_KEY_LENGTH 32
/**
- * How often Topology::clean() and Network::clean() and similar are called, in ms
+ * Minimum delay between timer task checks to prevent thrashing
*/
-#define ZT_HOUSEKEEPING_PERIOD 120000
+#define ZT_CORE_TIMER_TASK_GRANULARITY 500
/**
- * Overriding granularity for timer tasks to prevent CPU-intensive thrashing on every packet
+ * How often Topology::clean() and Network::clean() and similar are called, in ms
*/
-#define ZT_CORE_TIMER_TASK_GRANULARITY 500
+#define ZT_HOUSEKEEPING_PERIOD 120000
/**
* How long to remember peer records in RAM if they haven't been used
@@ -227,6 +227,11 @@
#define ZT_MULTICAST_LIKE_EXPIRE 600000
/**
+ * Period for multicast LIKE announcements
+ */
+#define ZT_MULTICAST_ANNOUNCE_PERIOD 120000
+
+/**
* Delay between explicit MULTICAST_GATHER requests for a given multicast channel
*/
#define ZT_MULTICAST_EXPLICIT_GATHER_DELAY (ZT_MULTICAST_LIKE_EXPIRE / 10)
@@ -239,12 +244,9 @@
#define ZT_MULTICAST_TRANSMIT_TIMEOUT 5000
/**
- * Delay between scans of the topology active peer DB for peers that need ping
- *
- * This is also how often pings will be retried to upstream peers (relays, roots)
- * constantly until something is heard.
+ * Delay between checks of peer pings, etc., and also related housekeeping tasks
*/
-#define ZT_PING_CHECK_INVERVAL 10000
+#define ZT_PING_CHECK_INVERVAL 5000
/**
* How frequently to send heartbeats over in-use paths
@@ -299,14 +301,6 @@
#define ZT_MIN_UNITE_INTERVAL 30000
/**
- * Delay between initial direct NAT-t packet and more aggressive techniques
- *
- * This may also be a delay before sending the first packet if we determine
- * that we should wait for the remote to initiate rendezvous first.
- */
-#define ZT_NAT_T_TACTICAL_ESCALATION_DELAY 1000
-
-/**
* Sanity limit on maximum bridge routes
*
* If the number of bridge routes exceeds this, we cull routes from the