7394ec6f6a
Prep in controller code to run tests.
11 years ago
a7bd1eaa40
Never assign v4 IPs ending in .255 even within range.
11 years ago
ddf3d1f949
Controller side support for IPv6 assignment.
11 years ago
610ab0750c
Drop Sqlite-based Log table for now and switch to an in-memory log for recent activity. Log table gets too big on busy nodes. Should probably support push of events to some kind of event system later.
11 years ago
ef316ced3b
Fix JSON.
11 years ago
cd005341c5
Extra statement to clean up Members -- cascade did not seem to work, possibly due to dual key.
11 years ago
a35fa7ac93
Add expansion of netconf in _test field.
11 years ago
bebe3d7cfa
Fix deadlock in test mode.
11 years ago
1f7a41cff8
Fix to allowing identity to be populated if not present.
11 years ago
4fbcad2468
Allow identity to be populated for newly inserted Member objects to permit transfer from old network controller and testing.
11 years ago
0d386f1c31
Add a bit of useful testing instrumentation to SqliteNetworkController.
11 years ago
2aa1b5d9b7
Add clock helper field to both member and network to permit time duration calculation easily.
11 years ago
9a5be0a092
typo
11 years ago
4da794b389
Add authorizedMemberCount to controller network config records.
11 years ago
0a5429cab0
Lookup of member must be a left outer join in case the member is being manually inserted before we see the node.
11 years ago
fcc5bf1e66
Go ahead and spec out controller DB support for AuthToken -- GitHub issue #211 -- even though full implementation won't make it into 1.0.4.
11 years ago
d57ea671d7
Add version to log.
11 years ago
d647a587a1
(1) Fix updating of network revision counter on member change.
...
(2) Go back to timestamp as certificate revision number. This is simpler
and more robust than using the network revision number for this and
forcing network revision fast-forward, which could cause some peers
to fall off the horizon when you don't want them to.
11 years ago
b3516c599b
Add a rate limiting circuit breaker to the network controller to prevent flooding attacks and race conditions.
11 years ago
3ba54c7e35
Eliminate some poorly thought out optimizations from the netconf/controller interaction,
...
and go ahead and bump version to 1.0.4.
For a while in 1.0.3 -dev I was trying to optimize out repeated network controller
requests by using a ratcheting mechanism. If the client received a network config
that was indeed different from the one it had, it would respond by instantlly
requesting it again.
Not sure what I was thinking. It's fundamentally unsafe to respond to a message
with another message of the same type -- it risks a race condition. In this case
that's exactly what could happen.
It just isn't worth the added complexity to avoid a tiny, tiny amount of network
overhead, so I've taken this whole path out.
A few extra bytes every two minutes isn't worth fretting about, but as I recall
the reason for this optimization was to save CPU on the controller. This can be
achieved by just caching responses in memory *there* and serving those same
responses back out if they haven't changed.
I think I developed that 'ratcheting' stuff before I went full time on this. It's
hard to develop stuff like this without hours of sustained focus.
11 years ago
e2a2993b18
Add a Log table to log queries for debugging and security logging. No JSON API support for querying the log yet, but will probably come via /network/###/member/###/log/... or something.
11 years ago
7c761dea72
Fix to member listing: I wanted an object with member IDs as keys and member revisions as values, not an array.
11 years ago
3f8a5b8b76
List members in the form of a hash of member ID and member revision so code can quickly detect which members have changed.
11 years ago
a061aa3d87
Remove "members" from Network record and instead enumerate members via specific query to /network/nwid/member sub-path. More RESTful, scalable, and compatible with how OnePoint code works.
11 years ago
b343eac10d
Fix IP auto-assign bug due to missing subnet routes.
11 years ago
649a12472b
Report controllerInstanceId in all objects so that controller resets can be easily detected by whatever is using the service.
11 years ago
cac6be87ba
Fix bug in rules JSON output.
11 years ago
38d34a7495
Proper handling of NULL entry for etherType in rules table.
11 years ago
fb4c3dd8d4
Fix string overwrite bug.
11 years ago
1ffd67e014
Get rid of false foreign key in Relay.
11 years ago
bca8886ff8
IP assignment pool range bug fix.
11 years ago
1f7bb67069
Fix some SQL and make instanceId more robustly random.
11 years ago
712e2785f2
Fix bad JSON in response.
11 years ago
5515909c1e
Add a concept of an "instanceId" to the controller, which the OnePoint can use to determine whether it is the same running database instance it already knows.
11 years ago
0db7c94c90
Add memberRevision stuff to JSON output, and update docs.
11 years ago
99969b186b
Add a concept of a member revision counter to networks. This can be used to select all members that have been added or changed since a given point.
11 years ago
f9f7de0ec7
Networks don't need their ID as a default name.
11 years ago
d27c14af48
Don't allow zero as a network number.
11 years ago
53c7f61f98
Fix for output of empty (no members) network
11 years ago
30e4a188d0
ipLocalRoutes now exposed via network objects in JSON controller API, and documentation changes.
11 years ago
5c9411a671
Untested -- modifications to support IP ranges instead of ip/mask for IP assignment pools, also add portId to Rule for future use.
11 years ago
48a2ad032a
(1) Both nodeId and portId in Rule can be NULL, (2) remove on delete cascade since rules should never mysteriously disappear from the rules table. If it let you delete a node with rules, that would be a UI or cleanup function bug.
11 years ago
f05e62deae
DB schema changes: separate portId in rules, ranges in IP assignment pools. (No code changes yet so code is broken.)
11 years ago
dbee1b38b3
Fix semantics of std::unique() to actually remove duplicates (hidden memory leak?)
11 years ago
57c7992c78
GitHub issue #191 - kill intra-network multicast rate limits (which were not 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.
11 years ago
3eca5d9c29
Fix reporting of ipAssignments for ipv4
11 years ago
50d4f66d73
Fixed member authorization bug and minor cleanup
11 years ago
16eae132fa
Fix for ipv4 assignment
11 years ago
4affa10ca0
Fix 404 on creation of new network
11 years ago
2e1d363a86
Removed a superfluous cross join
11 years ago
Adam Ierymenko
Kees Bos