 Adam Ierymenko
|
2cdda38dc4
It basically works... at least on current controllers.
|
9 years ago |
|
Adam Ierymenko
|
ccea3d04d6
Push NETWORK_CONFIG_REFRESH on POSTs to /member/... in controller.
|
9 years ago |
|
Adam Ierymenko
|
0a7a33ef8f
Instantaneous blacklisting and credential revocation.
|
9 years ago |
|
Adam Ierymenko
|
4d498b3765
Handling of multi-part chunked network configs on the inbound side.
|
9 years ago |
|
Adam Ierymenko
|
00fd9c3a15
It builds... almost ready to test some rules engine stuff.
|
9 years ago |
|
Adam Ierymenko
|
8007ca56aa
Refactor and tie-up of capabilities and tags and packet evaluation points. Some optimization is possible here but it is minor and we will make it work first.
|
9 years ago |
|
Adam Ierymenko
|
e2f783ebbd
.
|
9 years ago |
|
Adam Ierymenko
|
37d139177d
Integrate Filter into OutboundMulticast properly.
|
9 years ago |
|
Adam Ierymenko
|
e09c1a1c11
Big refactor mostly builds. We now have a uniform backward compatible netconf.
|
9 years ago |
|
Adam Ierymenko
|
4446dbde5e
Big refactor in service code to prep for plumbing through route management.
|
9 years ago |
|
Adam Ierymenko
|
90e1262a8b
More refactoring to remove old Dictionary dependencies.
|
9 years ago |
|
Adam Ierymenko
|
2f18a92e20
Cleanup in numerous places, reduce network chattiness around MULTICAST_LIKE, and fix a "how was that working" latent bug causing some control traffic to take the scenic route.
|
9 years ago |
|
Adam Ierymenko
|
51fecc0be9
Refactor Network for new NetworkConfig.
|
9 years ago |
|
Adam Ierymenko
|
6f854c8391
NetworkConfig refactor part 1
|
9 years ago |
|
Adam Ierymenko
|
4e4fd51117
boring doc stuff
|
9 years ago |
|
Adam Ierymenko
|
3883ac08c7
Docs and cleanup.
|
9 years ago |
|
Adam Ierymenko
|
d6f0f1a82a
Use network user ptr in lookup for Ethernet frame handling to eliminate map lookup.
|
9 years ago |
|
Adam Ierymenko
|
83ef98a9dc
Add a network-associated user ptr in API.
|
9 years ago |
|
Adam Ierymenko
|
35676217e8
Refactor multicast group announcement to work directly or indirectly.
|
9 years ago |
|
Adam Ierymenko
|
d6676a9d6c
Always announce multicast groups, not just to peers with direct links, and push network COMs to any MULTICAST_LIKE recipient for future use.
|
10 years ago |
|
Adam Ierymenko
|
9405150b11
Restore group announcement on Peer::receive() but centralize packet composition in one place.
|
10 years ago |
|
Adam Ierymenko
|
a3db7d0728
Refactor: move network COMs out of Network and into Peer in prep for tightening up multicast lookup and other things.
|
10 years ago |
|
Adam Ierymenko
|
f69454ec98
(1) Make ZT_ naming convention consistent (get rid of ZT1_), (2) Make local interface a full sockaddr_storage instead of an int identifier, which turns out to be better for multi-homing and other uses.
|
10 years ago |
|
Adam Ierymenko
|
307e44f7c8
Two for one! (std::map removal)
|
10 years ago |
|
Adam Ierymenko
|
d1341578d8
... and another one!
|
10 years ago |
|
Adam Ierymenko
|
7b8ce16057
Another std::map<> dies.
|
10 years ago |
|
Adam Ierymenko
|
778c7e6e70
More cleanup to direct path push, comment fixes, etc.
|
10 years ago |
|
Adam Ierymenko
|
f398952a6c
Revert some bad docs in Packet -- I think we will still use that. Also rename addMembershipCertificate to more security-descriptive validateAndAddMembershipCertificate, give it a return value, and drop unused force parameter.
|
10 years ago |
|
Adam Ierymenko
|
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.
|
10 years ago |
|
Adam Ierymenko
|
5e3c6d9e0d
Some nodeJS work, and apply fix from GitHub issue #166 plus a small optimization to avoid repeated calls to _allMulticastGroups().
|
10 years ago |
