| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
on inactive controllers.
|
|
|
|
|
|
slight changes in ZeroTier Central when it goes live.
|
|
|
|
|
|
network controller easier to refactor.
|
|
|
|
|
|
|
|
|
|
send the results when the test is queried later. This way you can POST a test and then come GET the result at the appointed time.
|
|
the main process itself to facilitate easier and safer backups of controller.db.
|
|
with valgrind.
|
|
CIRCUIT_TEST_REPORT messages.
|
|
|
|
recent activity. Log table gets too big on busy nodes. Should probably support push of events to some kind of event system later.
|
|
possibly due to dual key.
|
|
|
|
|
|
|
|
|
|
flooding attacks and race conditions.
|
|
API support for querying the log yet, but will probably come via /network/###/member/###/log/... or something.
|
|
easily detected by whatever is using the service.
|
|
use to determine whether it is the same running database instance it already knows.
|
|
select all members that have been added or changed since a given point.
|
|
documentation changes.
|
|
assignment pools, also add portId to Rule for future use.
|
|
well supported or easily configurable anyway) -- this is really left over from the old collaborative multicast propagation algorithm. New algorithm (in for a while) has been sender-side replication in which sender "pays" all bandwidth, which intrinsically limits multicast.
|
|
|
|
yet in client) toward GitHub issue #178
|
|
|
|
start on a NodeJS class for talking to the network controller.
|
|
|
|
convenience request in ControlPlane for scripted testing.
|
|
|
|
eliminating caching for now. We will re-add if it is needed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
for consistency.
|
