Check for (local multipath support only) during decision to decrease direct path push interval. This prevents the chicken-and-egg situation of not knowing if two peers can support multipath on both ends and thusly not sending eachother their direct paths quickly enough.
This commit is contained in:
parent
2e9fa7a811
commit
36d368cb78
2 changed files with 2 additions and 2 deletions
|
@ -553,7 +553,7 @@
|
|||
* peers of this peer's new link/address as soon as possible so that both peers can
|
||||
* begin forming an aggregated link.
|
||||
*/
|
||||
#define ZT_DIRECT_PATH_PUSH_INTERVAL_MULTIPATH ZT_DIRECT_PATH_PUSH_INTERVAL_HAVEPATH / 16
|
||||
#define ZT_DIRECT_PATH_PUSH_INTERVAL_MULTIPATH (ZT_DIRECT_PATH_PUSH_INTERVAL_HAVEPATH / 16)
|
||||
|
||||
/**
|
||||
* Time horizon for push direct paths cutoff
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue