2 ms·
Look at the netconf-master/ subfolder -- you can make private networks without using the web UI. But it's hard right now. It'll probably be made easier in the f
by api 12y ago
Look at the netconf-master/ subfolder -- you can make private networks without using the web UI. But it's hard right now. It'll probably be made easier in the future.
As far as pure decentralization goes: that's very hard, much harder than NAT-t and cryptography. I've prioritized zero-configuration instant-on and performance because that's what 95% of users want.
Here's a personal post I wrote on the difficulty:
http://adamierymenko.com/decentralization-i-want-to-believe/ http://adamierymenko.com/decentralization-i-want-to-believe/
- Rhapso 12y agoby netconf-master do you mean https://github.com/zerotier/ZeroTierOne/tree/master/netconf-service https://github.com/zerotier/ZeroTierOne/tree/master/netconf-... ?
- api 12y agoYep. It pulls the actual config from a Redis database. A 16-digit (64-bit) network ID consists of two parts: the 40-bit ZeroTier address of the node responsible for serving network configuration to members, and an arbitrary 24-bit network ID. When you join a network it just queries the netconf master for the network configuration. It's pretty simple. That's why all the network IDs you create at zerotier.com right now begin with the same 10-digit hexadecimal number. That's the ID of the node responsible for them and there's only one right now (though it's set up to fail over to another server, so it is fault tolerant). BTW... network configuration servers can go down and networks will keep working. You just can't change their configuration. So it's also fault tolerant in that way.