Adam Ierymenko
|
ccc73b920e
Node peer list function for CAPI, and some Peer cleanup.
|
hace 10 años |
Adam Ierymenko
|
c894710ac1
Remove Logger.hpp references.
|
hace 10 años |
Adam Ierymenko
|
49f031ccb4
Tons of refactoring, change to desperation algorithm to use max of core or link, porting over core loop code from old Node.cpp to new CAPI version, etc.
|
hace 10 años |
Adam Ierymenko
|
0a90681849
Add ping(), and a logic fix in SelfAwareness.
|
hace 10 años |
Adam Ierymenko
|
24608d5ca3
Always use HELLO to contact, and we now confirm newly learned paths via a two-way handshake to prevent half-connects.
|
hace 10 años |
Adam Ierymenko
|
52c3b7c34e
Implemented empirical determination of external addressing, paritioned per scope.
|
hace 10 años |
Adam Ierymenko
|
f4fd2d4971
Bring IncomingPacket into line with new changes.
|
hace 10 años |
Adam Ierymenko
|
6eb9289367
Bunch more cleanup, improvements to NAT traversal logic, finished updating Switch.
|
hace 10 años |
Adam Ierymenko
|
ee0f56355b
Send path simplification.
|
hace 10 años |
Adam Ierymenko
|
a69e1876f1
The concept of link desperation (escalating to less desirable transports) simplifies a ton of stuff. Loads of spaghetti logic can die since we no longer have to make these decisions down in the core.
|
hace 10 años |
Adam Ierymenko
|
7ff0cab1b7
docs
|
hace 10 años |
Adam Ierymenko
|
93012b0ee5
Re-incorporation: ZeroTier Networks -> ZeroTier, Inc. [Delaware]
|
hace 10 años |
Adam Ierymenko
|
0b84c10ccc
Add confirmation step to new netconf, with the caveat that it will be disabled for older netconf servers to avoid race. Also add some comments.
|
hace 11 años |
Adam Ierymenko
|
4e95384ad6
Cleanup, add tristate to config code in Network, and happy new year!
|
hace 11 años |
Adam Ierymenko
|
0e47f13f14
Simplify locking semantics some more to address a deadlock.
|
hace 11 años |
Adam Ierymenko
|
2416491cbc
Permanently retire peers.persist, but make iddb.d always enabled instead since identities are what we really want to cache.
|
hace 11 años |
Adam Ierymenko
|
6316011024
Make crypto and compression build optimized in debug, and also try disabling peers.persist -- might ship this way as it seems more trouble than its worth.
|
hace 11 años |
Adam Ierymenko
|
0d017c043f
Stop persisting last announcement time since Multicaster is volatile. Also some more legacy multicast fixes.
|
hace 11 años |
Adam Ierymenko
|
496109fdcc
Announce multicast group changes on network rescanMulticastGroups()
|
hace 11 años |
Adam Ierymenko
|
2659427864
Multicaster needs to be global, not per-network, and a bunch of other stuff.
|
hace 11 años |
Adam Ierymenko
|
050a0ce85d
.
|
hace 11 años |
Adam Ierymenko
|
81b12b6826
Rename the ubiquitous _r pointer to RuntimeEnvironment to RR just to be a little more consistent about using _ to denote private member variables.
|
hace 11 años |
Adam Ierymenko
|
1d37204a37
Refactoring in progress... pardon our dust...
|
hace 11 años |
Adam Ierymenko
|
4e9280fc7a
Rip out dead "firewall opener" code, replace in pipeline with anti-symmetric-NAT tactics.
|
hace 11 años |
Adam Ierymenko
|
c2187c8759
(1) distribute default root-topology in new dictionary format, (2) bump peer serialization version to force obsolescence of old supernodes, (3) stop outputting a log message every time we poll for software updates
|
hace 11 años |
Adam Ierymenko
|
8a804b5257
(1) Disable firewall openers (its easy to re-enable), (2) Do some prep work for making supernode topology hot-updatable.
|
hace 11 años |
Adam Ierymenko
|
88bdb81791
Keep track of basic aliveness for peers regardless if direct or indirect connectivity and use this for multicast propagation. Also consolidate adding of active bridges via the same functor as regular multicast next hops.
|
hace 11 años |
Adam Ierymenko
|
7831c4bfef
Cleanup, dead code removal, some pretty insignificant security stuff that's based on recommendations.
|
hace 11 años |
Adam Ierymenko
|
aee742e767
More toward GitHub issue #56
|
hace 11 años |
Adam Ierymenko
|
b117ff5435
Probable fix for GitHub issue #63 - do not unite() if either path is TCP, since doing so can result in asymmetric failed NAT-t over UDP if one side has a firewall that permits outgoing UDP but not incoming.
|
hace 11 años |