travis laduke 82c799b9d1 Expose surface addresses in info json
Surface Addresses are the addresses that
the roots report back to you.

This is helpful for trouble shooting.

If you're behind NAT, the source port is different
than what zerotier is bound to.
If the list of surface address ports is larger than the list of
bound addresses, you are probably behind symmetric NAT.

Anways this can be added to later with a more simple
"easy" or "hard" nat computed message somewhere.
2022-10-25 11:25:21 -07:00
..
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2020-08-21 14:23:31 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2020-08-21 14:23:31 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2021-12-03 15:44:04 -08:00
2022-06-06 16:18:50 -04:00
2022-10-25 11:25:21 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2020-11-16 16:30:15 -05:00
2020-08-20 12:51:39 -07:00
2022-02-25 11:29:07 -08:00
2022-04-19 21:30:36 -04:00
2020-08-20 12:51:39 -07:00
2017-02-03 19:47:00 -08:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2018-06-07 17:25:27 -07:00
2020-08-21 14:23:31 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
2022-02-15 09:13:58 -05:00
2020-08-20 12:51:39 -07:00
2020-08-20 12:51:39 -07:00
yes
2021-04-13 16:12:11 +00:00
2020-08-20 12:51:39 -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.