2.6 KiB
Frequently Asked Questions
Can I use this in my commercial or closed-source application or service?
Yes! - Just let us know, and we will work out a licensing scheme. You will need to build the library with the lwIP network stack. In the case that you're a non-profit, or are developing open source software, you can use this entirely for free and may choose either picoTCP or lwIP as your network stack.
My application or service won't fully come online
In rare circumstances it can take a substantial amount of time for a libzt instance to come online and become reachable. In cases where it never seems to progress beyond this stage you should check to make sure there are no rogue processes on the machines using the same ZeroTier identity files, or no other instances on your ZeroTier network using said identity files. If this doesn't help. Contact us.
How do I get debug output?
In order of relevance, enable the following: For libzt-specific debug output which basically includes the POSIX socket emulation layer and network stack drivers, enable LIBZT_DEBUG=1. For situations where you suspect that the problem might lie within the network stack itself, enable NS_DEBUG=1. You should also check out include/libzt.h for additional fine-grained debug options for each network stack. If you think that your problem is with the ZeroTier protocol itself, enable ZT_DEBUG=1. This will output what's happening in the ZeroTier core. Note, you can enable all of these at once if you're brave. Additionally, you can use the LIBZT_SANITIZE=1 flag to build against the AddressSanitization library.
Versioning
Each version of libzt will include a specific (and unrelated) version of the ZeroTier core, and network stacks. For instance: Version 1.1.5 of libzt might include version 1.2.5 of ZeroTier, there is no connection between these versioning schemes. Additionally, an update to libzt doesn't necessarily translate to an update to the ZeroTier core.
Code Quality and Standardization
Explicit coding style rules are specified in test/vera++/libzt and enforced periodically by running the source through vera++. Before each commit or merge into master one should run test/selftest and test/nativetest as specified in TESTING.md. Also, on the tabs vs. spaces debate, for this project we have chosen tabs.
How do I run unit tests?
See: TESTING.md