A Smart Ethernet Switch for Earth
Go to file
2015-06-01 17:50:44 -07:00
artwork Add signed binary build of Mac GUI wrapper. 2015-05-17 19:48:21 -07:00
attic Clean old netconf-service from attic. 2015-05-26 18:16:12 -07:00
controller Go ahead and add flags and invFlags to the Rule table. 2015-05-25 13:20:10 -07:00
ext Fix for GitHub issue #133, and move restart out of installer to address restart problem. Installer probably should NOT mess with the running service, since Linux servers are likely to be production. 2015-05-27 13:50:11 -07:00
include 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. 2015-05-21 15:58:26 -07:00
js/zt1-api-client Delete some temporary code. 2015-05-26 13:34:08 -07:00
node Rest of GitHub issue #140 implementation. 2015-06-01 17:50:44 -07:00
osdep Add some proxy debugging, and auto-resolve and periodically re-resolve TCP fallback tunnel hostname. 2015-05-21 15:22:41 -07:00
root-topology Fix to create-test-root-topology. 2015-04-30 16:13:17 -07:00
service Right now only FreeBSD can use BSDEthernetTap, which will probably get renamed accordingly. NetBSD and OpenBSD do not support tap, only tun, so they will have to wait. 2015-05-25 11:11:37 -07:00
tcp-proxy TCP fallback tunneling is now working. That hurt more than expected. 2015-05-22 14:52:23 -07:00
ui A visit to the Windows house of pain: 2015-05-18 20:30:54 -07:00
windows Add BackgroundResolver to Windows build. 2015-06-01 16:06:50 -07:00
.gitignore Clean old netconf-service from attic. 2015-05-26 18:16:12 -07:00
AUTHORS.txt docs 2015-04-16 16:15:25 -07:00
BUILDING.md docs 2015-04-17 10:45:16 -07:00
LICENSE.txt New git repository for release - version 0.2.0 tagged 2013-07-04 16:56:19 -04:00
make-freebsd.mk CLI work and Makefile cleanup. 2015-04-16 15:07:58 -07:00
make-linux.mk Fix installer path, add netconf option to make-linux. 2015-05-28 03:13:23 +00:00
make-mac.mk Apple auto-update stuff, now for Windows. 2015-05-20 19:38:49 -07:00
Makefile Basic OpenBSD compile fixes -- still need to update BSDEthernetTap, will do that later. Should be able to re-use FreeBSD port for OpenBSD, but we will see. 2015-05-15 08:48:53 -07:00
objects.mk Background resolver. 2015-05-21 13:44:33 -07:00
one.cpp Ground work for reincorporating software updater for select platforms. 2015-05-20 16:35:33 -07:00
README.md Rename netconf to controller and NetworkConfigMaster to NetworkController for consistency. 2015-04-15 15:12:09 -07:00
RUNNING.md FreeBSD works, and some documentation fixes. 2014-12-19 15:18:20 -08:00
selftest.cpp BackgroundResolver test. 2015-05-21 14:11:44 -07:00
version.h Re-incorporation: ZeroTier Networks -> ZeroTier, Inc. [Delaware] 2015-02-17 13:11:34 -08:00

ZeroTier One - Network Virtualization Everywhere

ZeroTier One is an ethernet virtualization engine. It creates virtual switched LANs of almost unlimited size that span physical network boundaries. To the operating system these behave just like ordinary Ethernet ports. Everything just works, even as your computer moves around or your physical Internet link changes.

It's intended to replace conventional hub-and-spoke VPNs, provide provider-neutral secure private backplane networks to multi-data-center and hybrid cloud deployments, allow remote access to embedded devices, and much more.

ZeroTier uses a peer to peer network with managed anchor points ("supernodes"). These are operated by ZeroTier Networks, and are free to use. They provides instant "zero configuration" startup, NAT traversal assistance, relaying in cases where NAT traversal doesn't work, and a trusted root authority for looking up peer public keys (identities). The supernodes run the same open-source software as regular nodes, are geographically distributed across three continents, and have remained stable for over a year. This blog post discusses the design rationale in some detail. (TL;DR: this design represents a compromise between speed and ease of use and decentralization.)

ZeroTier One encrypts all traffic end-to-end with keys that only you control. Even when traffic is traversing our network we cannot decrypt it. It's not, however, a "strong privacy" tool since it would still be possible for us (or your ISP or anyone else in between) to observe "meta-data" about your traffic. If you need that level of anonymity, we recommend Tor or something similar. Onion routing is the only technology we're aware of that is capable of delivering that level of end-to-end privacy protection.

At the moment the ZeroTier wire protocol is only documented in the source (start with the comments in Packet.hpp), but more formal documentation is planned for the near future. Encapsulation overhead is comparable to IPSec or OpenVPN.

Visit ZeroTier Networks on the web for more information. Follow the ZeroTier blog, Twitter feed and the main GitHub project to stay up to date. See the GitHub-hosted wiki (sidebar) for more technical info and help for various platforms. There's also a support portal for more general information.

Getting Started

Auto-updating binary packages that install easily can be found here for officially supported platforms. Packages for popular Linux distributions that neatly wrap the Linux installer/uninstaller are coming soon.

If you want to build from source, clone this repository and see BUILDING.txt and RUNNING.txt. If you build manually you'll have to update manually, and we recommend doing so often as development is progressing very rapidly. (Protocol is pretty stable but you might miss out on new features or experience performance degradation if you're too far behind.)

Once you are up and running, you have several options.

ZeroTier provides ZeroTier One for free, but to help finance development and operations we have a user-friendly freemium control panel on the web. This control panel lets you quickly and easily create your own networks, and the operation of their controller node(s) is left to us. Public networks created on our site are free, and private networks are free for up to ten devices. After that there is a monthly charge.

You only need an account on our site if you want to use the control panel found there. Joining networks requires no account. To get authorized on a private network, just send your device's 10-digit ID to the network's administrator and they can add you.

Public networks, as the name implies, can be joined without getting authorization from anyone. All you need is their 16-digit network ID. A public network called Earth (8056c2e21c000001) exists for everyone, but be sure your device is adequately secured and up to date before joining.

More products and services will be forthcoming.

Basic Troubleshooting

For about 95% of users, it just works.

If you are running a local system firewall, we recommend adding a rule permitting UDP port 9993 inbound and outbound. The binary Windows installer takes care of this for Windows' built-in firewall, but other platforms and third party firewall software may need this for optimal performance.

ZeroTier One peers will automatically locate each other and communicate directly over a local wired LAN if UDP port 9993 inbound is open. If that port is filtered, they won't be able to see each others' LAN announcement packets. If you're experiencing poor performance between devices on the same physical network, check their firewall settings. Without LAN auto-location peers must attempt "loopback" NAT traversal, which sometimes fails and in any case requires that every packet traverse your external router twice.

Users behind certain types of firewalls and "symmetric" NAT devices may not able able to connect to external peers directly at all. ZeroTier has limited support for port prediction and will attempt to traverse symmetric NATs, but this doesn't always work. If P2P connectivity fails you'll be bouncing UDP packets off our relay servers resulting in slower performance. Some NAT router(s) have a configurable NAT mode, and setting this to "full cone" will eliminate this problem. If you do this you may also see a magical improvement for things like VoIP phones, Skype, BitTorrent, WebRTC, certain games, etc., since all of these use NAT traversal techniques similar to ours.

If you're interested, there's a technical deep dive about NAT traversal on our blog. A troubleshooting tool to help you diagnose NAT issues is planned for the future as are uPnP/IGD/NAT-PMP and IPv6 transport.

If a firewall between you and the Internet blocks ZeroTier's UDP traffic, you will fall back to last-resort TCP tunneling to supernodes over port 443 (https impersonation). This will work almost anywhere but is slow. If performance seems just terrible, this is the first thing to check.

Some Windows users have reported a problem with the TAP device driver. From user reports this seems to occur on Windows systems that have not been updated through Windows Update. While we have a fix planned, we really recommend keeping your system up to date for security reasons. Frankly we're a bit torn on this one. If this is truly the cause, perhaps ZeroTier failing to work on unpatched Windows systems is a feature not a bug.

More help can be found in the GitHub wiki and the customer support portal / knowledge base.

The ZeroTier source code is open source and is licensed under the GNU GPL v3 (not LGPL). If you'd like to embed it in a closed-source commercial product or appliance, please e-mail contact@zerotier.com to discuss licensing.

ZeroTier is keyboard crafted with coffee and sleep deprivation in Southern California.