 Adam Ierymenko
|
d6a1868d0a
Refactor incoming packet (rxQueue/fragmentQueue) to eliminate variable length queues and merge queues. This is both faster and saves memory.
|
9 years ago |
|
Adam Ierymenko
|
4e4fd51117
boring doc stuff
|
9 years ago |
|
Adam Ierymenko
|
704205c5f7
Dead code removal.
|
9 years ago |
|
Adam Ierymenko
|
436c1fac1d
Selectively move over changes from "edge" to "dev" excluding netcon.
|
9 years ago |
|
Adam Ierymenko
|
9490b1f136
Try prioritizing cluster-send over direct send in cluster mode -- may improve cluster relaying reliability.
|
9 years ago |
|
Adam Ierymenko
|
f692cec763
Change how cluster relays packets -- just PROXY_UNITE and then send packet via normal ZeroTier front plane -- more efficient and eliminates fragmentation issues.
|
9 years ago |
|
Adam Ierymenko
|
f69454ec98
(1) Make ZT_ naming convention consistent (get rid of ZT1_), (2) Make local interface a full sockaddr_storage instead of an int identifier, which turns out to be better for multi-homing and other uses.
|
10 years ago |
|
Adam Ierymenko
|
367ffde00c
Plumb through localInterfaceId to track local interfaces corresponding with remote addresses.
|
10 years ago |
|
Adam Ierymenko
|
85b90f122a
Final std::map<> from Switch, and add some smallish default values for hash size.
|
10 years ago |
|
Adam Ierymenko
|
3dba016a93
Almost done... very few std::map<>s remaining in any spot that matters.
|
10 years ago |
|
Adam Ierymenko
|
db0369e9b8
Remove way-overkill multimap from Switch.
|
10 years ago |
|
Adam Ierymenko
|
0ab3e49be9
Starting in on Switch... kill map in defrag queue, which will probably improve performance pretty decently under high load with lots of peers.
|
10 years ago |
|
Adam Ierymenko
|
b31071463c
Try another NAT traversal improvement.
|
10 years ago |
|
Adam Ierymenko
|
fe20f0d7cd
Put back legacy code to listen for LAN announcements to support same network location with pre-1.0.4 clients.
|
10 years ago |
|
Adam Ierymenko
|
41fc08b330
etherTypeName() is only used in Switch and only with ZT_TRACE
|
10 years ago |
|
Adam Ierymenko
|
07ea4fd4f9
Fix potential bug in controller config request.
|
10 years ago |
|
Adam Ierymenko
|
778c7e6e70
More cleanup to direct path push, comment fixes, etc.
|
10 years ago |
|
Adam Ierymenko
|
79e9a8bcc2
Almost everything for GitHub issue #180 except direct path map setup.
|
10 years ago |
|
Adam Ierymenko
|
960ceb4791
Rest of GitHub issue #140 implementation.
|
10 years ago |
|
Adam Ierymenko
|
196f27f1f0
Add delay to NAT-t escalation stuff to try to address GitHub issue #167
|
10 years ago |
|
Adam Ierymenko
|
d9006712f6
Completely factor out "desperation" from the core. I thought of a 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.
|
10 years ago |
|
Adam Ierymenko
|
c894710ac1
Remove Logger.hpp references.
|
10 years ago |
|
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.
|
10 years ago |
|
Adam Ierymenko
|
6eb9289367
Bunch more cleanup, improvements to NAT traversal logic, finished updating Switch.
|
10 years ago |
|
Adam Ierymenko
|
ee0f56355b
Send path simplification.
|
10 years ago |
|
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.
|
10 years ago |
|
Adam Ierymenko
|
93012b0ee5
Re-incorporation: ZeroTier Networks -> ZeroTier, Inc. [Delaware]
|
10 years ago |
|
Adam Ierymenko
|
4e95384ad6
Cleanup, add tristate to config code in Network, and happy new year!
|
10 years ago |
|
Adam Ierymenko
|
e7c81ef34e
Turns out that needed to be a list after all. Also clean up Multicaster::gather().
|
10 years ago |
|
Adam Ierymenko
|
ae082c3cb8
Yay... now everything compiles! Getting close to testing on this. Still have 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.
|
11 years ago |
