Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Loading the peer dirs directly led to peers being discovered in a different
order after reconfigure.
|
|
|
|
|
|
It is now included in the version string itself.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
actually established
Doing so could lead to duplicate address entries in different peers, causing
very strange behaviour.
Add additional parameters for the local and the peer address to
fastd_shell_exec() to allow the on-verify script to use this information
nevertheless.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A random splay time of up to 5 minutes will ensure that simultaneous handshakes
with many peers are desynchronized as fast as possible.
|
|
|
|
|
|
|
|
Directly using the peers allows us to get rid of the inefficient get_peer()
function and is necessary for adding support for unknown peers.
|
|
This can lead to handshakes being ignored for an indefinite time.
|
|
Shouldn't make a difference, but feels cleaner now, and silences a
clang-analyzer warning.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This isn't our job, so there is no reason to support this.
|
|
|
|
|
|
|