mirror of
https://github.com/zerotier/ZeroTierOne.git
synced 2026-02-28 10:42:47 -08:00
| .. | ||
| Address.hpp | ||
| Array.hpp | ||
| AtomicCounter.hpp | ||
| Buffer.hpp | ||
| C25519.cpp | ||
| C25519.hpp | ||
| Capability.cpp | ||
| Capability.hpp | ||
| CertificateOfMembership.cpp | ||
| CertificateOfMembership.hpp | ||
| Cluster.cpp | ||
| Cluster.hpp | ||
| Constants.hpp | ||
| Dictionary.hpp | ||
| Hashtable.hpp | ||
| Identity.cpp | ||
| Identity.hpp | ||
| IncomingPacket.cpp | ||
| IncomingPacket.hpp | ||
| InetAddress.cpp | ||
| InetAddress.hpp | ||
| MAC.hpp | ||
| Membership.cpp | ||
| Membership.hpp | ||
| Multicaster.cpp | ||
| Multicaster.hpp | ||
| MulticastGroup.hpp | ||
| Mutex.hpp | ||
| Network.cpp | ||
| Network.hpp | ||
| NetworkConfig.cpp | ||
| NetworkConfig.hpp | ||
| NetworkController.hpp | ||
| Node.cpp | ||
| Node.hpp | ||
| NonCopyable.hpp | ||
| OutboundMulticast.cpp | ||
| OutboundMulticast.hpp | ||
| Packet.cpp | ||
| Packet.hpp | ||
| Path.cpp | ||
| Path.hpp | ||
| Peer.cpp | ||
| Peer.hpp | ||
| Poly1305.cpp | ||
| Poly1305.hpp | ||
| README.md | ||
| Revocation.cpp | ||
| Revocation.hpp | ||
| RuntimeEnvironment.hpp | ||
| Salsa20.cpp | ||
| Salsa20.hpp | ||
| SelfAwareness.cpp | ||
| SelfAwareness.hpp | ||
| SHA512.cpp | ||
| SHA512.hpp | ||
| SharedPtr.hpp | ||
| Switch.cpp | ||
| Switch.hpp | ||
| Tag.cpp | ||
| Tag.hpp | ||
| Topology.cpp | ||
| Topology.hpp | ||
| Utils.cpp | ||
| Utils.hpp | ||
| World.hpp | ||
ZeroTier Virtual Switch 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.