Age | Commit message (Collapse) | Author |
|
|
|
|
|
decided to put it in to prep for future QoS support and SD-WAN stuff.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
allow user to specify arbitrary allowed IP networks in allowManaged
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
multicast on the network as would be expected.
|
|
normally use expired paths. Expired paths might still be tried if nothing else is reachable.
|
|
|
|
|
|
json-parser to eliminate a dependency.
|
|
server targets. Also means that ZeroTier One now requires C++11. (Still keeping C++11 out of the core in node/ though.)
|
|
|
|
|
|
all through via the JSON API. Default route and route management stuff just about done.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
interface a full sockaddr_storage instead of an int identifier, which turns out to be better for multi-homing and other uses.
|
|
full identity of peers instead of just address.
|
|
|
|
|
|
Multiple statements in a sqlite3_prepare_v2 is not usable. Only
the first statement will be executed.
Since the schema now uses 'ON DELETE CASCADE', there's only
one statement needed.
If multiple statements are needed, there should be either multiple
sqlite3_prepare_v2 calls be used or the sqlite3_exec function.
|
|
|
|
|
|
|