ZeroTierOne/node
Adam Ierymenko 6914425b03 cleanup
2019-03-28 13:58:19 -07:00
..
Address.hpp
AtomicCounter.hpp
Buffer.hpp Get rid of ZT_FAST_MEMCPY because this is not really needed. 2019-03-22 15:50:15 -07:00
C25519.cpp Never mind, only unused on some builds so leave them there. 2019-03-27 09:30:45 -07:00
C25519.hpp
Capability.cpp
Capability.hpp Various other fixes including removal of more mem*() issues and netlink fixes for AARCH64. 2019-03-25 22:19:52 +00:00
CertificateOfMembership.cpp
CertificateOfMembership.hpp Get rid of some mem* calls that are bad C++ form (but worked fine) and cause warnings. 2019-03-25 11:45:32 -07:00
CertificateOfOwnership.cpp
CertificateOfOwnership.hpp Nope, more... 2019-03-25 12:56:03 -07:00
Constants.hpp
Credential.hpp
Dictionary.hpp
Hashtable.hpp
Identity.cpp
Identity.hpp Get rid of ZT_FAST_MEMCPY because this is not really needed. 2019-03-22 15:50:15 -07:00
IncomingPacket.cpp
IncomingPacket.hpp
InetAddress.cpp cleanup 2019-03-28 13:58:19 -07:00
InetAddress.hpp Get rid of ZT_FAST_MEMCPY because this is not really needed. 2019-03-22 15:50:15 -07:00
MAC.hpp
Membership.cpp
Membership.hpp
Multicaster.cpp
Multicaster.hpp
MulticastGroup.hpp
Mutex.hpp
Network.cpp Get rid of ZT_FAST_MEMCPY because this is not really needed. 2019-03-22 15:50:15 -07:00
Network.hpp
NetworkConfig.cpp Various other fixes including removal of more mem*() issues and netlink fixes for AARCH64. 2019-03-25 22:19:52 +00:00
NetworkConfig.hpp One more. 2019-03-25 12:36:54 -07:00
NetworkController.hpp
Node.cpp Get rid of ZT_FAST_MEMCPY because this is not really needed. 2019-03-22 15:50:15 -07:00
Node.hpp
OutboundMulticast.cpp Get rid of ZT_FAST_MEMCPY because this is not really needed. 2019-03-22 15:50:15 -07:00
OutboundMulticast.hpp
Packet.cpp Get rid of ZT_FAST_MEMCPY because this is not really needed. 2019-03-22 15:50:15 -07:00
Packet.hpp
Path.cpp
Path.hpp Get rid of ZT_FAST_MEMCPY because this is not really needed. 2019-03-22 15:50:15 -07:00
Peer.cpp Temporarily disable the symmetric NAT port prediction code since the current version adds protocol overhead and probably is not that effective. 2019-03-26 15:23:51 -07:00
Peer.hpp
Poly1305.cpp
Poly1305.hpp
README.md
Revocation.cpp
Revocation.hpp ... 2019-03-25 12:58:43 -07:00
RingBuffer.hpp
RuntimeEnvironment.hpp
Salsa20.cpp
Salsa20.hpp
SelfAwareness.cpp Temporarily disable the symmetric NAT port prediction code since the current version adds protocol overhead and probably is not that effective. 2019-03-26 15:23:51 -07:00
SelfAwareness.hpp Temporarily disable the symmetric NAT port prediction code since the current version adds protocol overhead and probably is not that effective. 2019-03-26 15:23:51 -07:00
SHA512.cpp
SHA512.hpp
SharedPtr.hpp
Switch.cpp
Switch.hpp
Tag.cpp
Tag.hpp Various other fixes including removal of more mem*() issues and netlink fixes for AARCH64. 2019-03-25 22:19:52 +00:00
Topology.cpp
Topology.hpp
Trace.cpp
Trace.hpp
Utils.cpp
Utils.hpp Get rid of ZT_FAST_MEMCPY because this is not really needed. 2019-03-22 15:50:15 -07:00
World.hpp Get rid of ZT_FAST_MEMCPY because this is not really needed. 2019-03-22 15:50:15 -07:00

ZeroTier Network Hypervisor Core

This directory contains the real ZeroTier: a completely OS-independent global virtual Ethernet switch engine. This is where the magic happens.

Give it wire packets and it gives you Ethernet packets, and vice versa. The core contains absolutely no actual I/O, port configuration, or other OS-specific code (except Utils::getSecureRandom()). It provides a simple C API via /include/ZeroTierOne.h. It's designed to be small and maximally portable for future use on small embedded and special purpose systems.

Code in here follows these guidelines:

  • Keep it minimal, especially in terms of code footprint and memory use.
  • There should be no OS-dependent code here unless absolutely necessary (e.g. getSecureRandom).
  • If it's not part of the core virtual Ethernet switch it does not belong here.
  • No C++11 or C++14 since older and embedded compilers don't support it yet and this should be maximally portable.
  • Minimize the use of complex C++ features since at some point we might end up "minus-minus'ing" this code if doing so proves necessary to port to tiny embedded systems.