| Age | Commit message (Collapse) | Author |
|---|
|
|
|
messages from being sent.
|
|
|
|
|
|
|
|
improve cluster relaying reliability.
|
|
|
|
responses if the addressing scheme matches -- this allows multicast-free instant lookup of local IPv6 for better performance and reliability.
|
|
|
|
|
|
|
|
via normal ZeroTier front plane -- more efficient and eliminates fragmentation issues.
|
|
|
|
|
|
|
|
tightening up multicast lookup and other things.
|
|
interface a full sockaddr_storage instead of an int identifier, which turns out to be better for multi-homing and other uses.
|
|
remote addresses.
|
|
size.
|
|
|
|
|
|
improve performance pretty decently under high load with lots of peers.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ineffective.
|
|
location with pre-1.0.4 clients.
|
|
and replacing it with a simple non-crypto PRNG that just uses Salsa20.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
support code in Switch.
|
|
well supported or easily configurable anyway) -- this is really left over from the old collaborative multicast propagation algorithm. New algorithm (in for a while) has been sender-side replication in which sender "pays" all bandwidth, which intrinsically limits multicast.
|
|
full identity of peers instead of just address.
|
|
|
|
allow RENDEZVOUS from regular peers.
|
|
|
|
|
|
|
|
|
|
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.
|
