Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Now that peers have a peer id we can use that to specify a peer in a resolve
return. As the remote list of a peer doesn't change without the peer id
changing, instead of taking a remote ref we can just use the peer id and remote
index.
|
|
established peers
|
|
they aren't configured statically
|
|
|
|
|
|
|
|
The new poll code has made this second peer list obsolete.
|
|
|
|
|
|
implementations
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
invalid aliasing (hopefully)
|
|
|
|
The monotone timestamp is near zero on linux systems, confusing fastd.
|
|
The handshakes are now schedules in a doubly-linked list that is maintained as a
part of the peer structure.
|
|
handshake finish
This ensures that the handshake is repeated in case the finish packet is lost.
|
|
This is needed at least on FreeBSD
|
|
Everything clang and GCC warn about, except GCC's missing-field-initializers
which are just stupid as they don't allow {} syntax to zero a field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|