| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
encryption as a precaution.
|
|
upstreams are. These are not used yet but will be needed for future privacy modes, etc. Also some cleanup.
|
|
|
|
possibly GitHub #443
|
|
|
|
|
|
|
|
rapid setup. Will need to revisit later.
|
|
multicast on the network as would be expected.
|
|
|
|
since they will need them to push auth for multicast stuff, (2) added a bunch of rate limit circuit breakers for anti-DOS, (3) cleanup.
|
|
pushes and simplify code.
|
|
normally use expired paths. Expired paths might still be tried if nothing else is reachable.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
more rules with better space efficiency.
|
|
and fix a "how was that working" latent bug causing some control traffic to take the scenic route.
|
|
|
|
needing to traverse the whole queue array.
|
|
support).
|
|
|
|
|
|
length queues and merge queues. This is both faster and saves memory.
|
|
received-on address to eliminate false symmetric classification.
|
|
compatibility bugs when the latter was modified due to timer interactions with other versions.
|
|
|
|
than 10 seconds at a very small cost in ECHO requests (or HELLOs for older peers). GitHib issue #272
|
|
1.1.3 (dev)
|
|
|
|
Otherwise, local discovered routes are ignored.
Don't know what the best value would be. Taking 4 for now.
|
|
(e.g. 300+ms from New York to Johhannesburg)
|
|
|
|
|
|
|
