| Age | Commit message (Collapse) | Author |
|---|
|
|
|
significantly simpler way to move all of this logic entirely into the containing service, liberating the core from any concern over the nature of its pipe to the outside world.
|
|
never work.
|
|
avoid flooding.
|
|
core, other bug fixes.
|
|
direct links.
|
|
|
|
|
|
|
|
link, porting over core loop code from old Node.cpp to new CAPI version, etc.
|
|
two-way handshake to prevent half-connects.
|
|
|
|
|
|
|
|
Switch.
|
|
|
|
simplifies a ton of stuff. Loads of spaghetti logic can die since we no longer have to make these decisions down in the core.
|
|
|
|
|
|
current one it attempts.
|
|
refactoring, and a few other things related to multicast.
|
|
multicast for debugging purposes.
|
|
of certificates of membership.
|
|
that differently, re-add support for active bridges, and remove some gratuitous use of std::set where not needed.
|
|
Multicaster::gather().
|
|
|
|
|
|
not added backward compatibility support for relaying of multicasts to 0.9.X clients yet but that will be easy. Will test with heterogenous 1.0.0 clients only first.
|
|
|
|
little more consistent about using _ to denote private member variables.
|
|
|
|
|
|
|
|
anti-symmetric-NAT tactics.
|
|
supernode if I am a supernode. Also some comment cleanup.
|
|
for making supernode topology hot-updatable.
|
|
connectivity and use this for multicast propagation. Also consolidate adding of active bridges via the same functor as regular multicast next hops.
|
|
Otherwise a dead active bridge might kill multicast for us.
|
|
|
|
size thinko.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
latent probably-never-triggered bug in MULTICAST_FRAME handling. GitHub issue #68
|
|
|
|
|
|
|
