1
0
mirror of https://github.com/XeonSquared/OC-Copper.git synced 2024-11-14 22:08:05 +11:00
Commit Graph

4 Commits

Author SHA1 Message Date
20kdc
9df9823a4f Clarify possibilities of interaction between broadcast packets and hierarchial gateways.
The implementation in the oc/ subfolder of a hierarchial gateway goes
with the "allow subnets to cause higher-level broadcasts, and allow
 higher levels to cause subnet broadcasts, but don't let messages leak"
 solution
That is, the default if hierarchial gateways have no special
 handling for broadcast addresses.
2017-03-20 16:20:52 +00:00
20kdc
c91f3bd2a9 Be more explicit in protocol.1 about packet alterations, add license header to occure.lua 2017-03-20 00:33:06 +00:00
gamemanj
47ec74bc89 Lowered protocol packet size limit and changed how it's calculated, also changed testcase to be slightly less worst-case.
The previous testcase was "all nodes communicating randomly", basically a worst-case.
This testcase is somewhat more realistic, a set of nodes communicating between each other via other
 nodes, a given TO node recurring once every 5 seconds (approximately).
Notably, the 'packet transfer total' figure should be halved, as in the testcase pings and responses
 are used, but only responses are counted.
2017-03-18 12:28:46 +00:00
20kdc
2b458b5df8 Add incomplete workspace, for now. 2017-03-18 09:37:56 +00:00