| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
explicitly check whether paths should be used. Check in with this callback (if present) when learning new paths or sending initial packets.
|
|
more explicit methods.
|
|
|
|
1.1.3 (dev)
|
|
|
|
|
|
|
|
|
|
|
|
add a legacy hack for older clients working with clusters.
|
|
|
|
|
|
|
|
|
|
|
|
rate limiting in PUSH_DIRECT_PATHS for now (but we will do something else to mitigate amplification attacks)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
vector.
|
|
|
|
from other Worlds.
|
|
|
|
|
|
|
|
|
|
updates.
|
|
|
|
and upstream hop in graph traversal history.
|
|
|
|
CIRCUIT_TEST_REPORT messages.
|
|
|
|
|
|
|
|
|
|
|
|
serialize/deserialize into the class.
|
|
|
|
|
|
|
|
|
|
tightening up multicast lookup and other things.
|
|
|
