izaya/OC-Copper
1
0
Fork 0
mirror of https://github.com/XeonSquared/OC-Copper.git synced 2024-11-15 06:18:05 +11:00
Code Issues Releases Wiki Activity

Be more explicit in protocol.1 about packet alterations, add license header to occure.lua

Browse Source
This commit is contained in:
20kdc 2017-03-20 00:33:06 +00:00
parent a998d3412c
commit c91f3bd2a9
2 changed files with 17 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
oc/occure.lua
View File

@ -1,3 +1,6 @@
-- I, 20kdc, release this into the public domain.
-- No warranty is provided, implied or otherwise.
-- OC/CU/RE Driver -- OC/CU/RE Driver
-- (Copper w/Reliability Layer on OpenComputers/OpenOS) -- (Copper w/Reliability Layer on OpenComputers/OpenOS)
-- I, 20kdc, release this into the public domain. -- I, 20kdc, release this into the public domain.

18
protocol.1
View File

@ -9,16 +9,26 @@ They are simply base low-level Copper nodes with two interfaces and the
For the FROM address: For the FROM address:
If it's on the parent side, reject if it's prefixed with hostname .. "/", If it's on the parent side, reject if it's prefixed with hostname .. "/",
otherwise prefix it with "<" and forward to child side. otherwise prefix it with "<".
If it's on the child side, reject if it's prefixed with "<", If it's on the child side, reject if it's prefixed with "<",
otherwise prefix it with hostname .. "/" and forward to parent side. otherwise prefix it with hostname .. "/".
For the TO address: For the TO address:
If it's on the parent side, reject unless prefixed with hostname .. "/", If it's on the parent side, reject unless prefixed with hostname .. "/",
otherwise remove that and forward to child side. otherwise remove that.
If it's on the child side, reject unless prefixed with "<", If it's on the child side, reject unless prefixed with "<",
otherwise remove that and forward to parent side. otherwise remove that.
For the packet's general routing:
If it's on the parent side, run the rules above on the addresses,
and forward to child side if not rejected.
If it's on the child side, run the rules above on the addresses,
and forward to parent side if not rejected.
Notably, the hops field should be incremented as if going through a normal routing node -
this prevents system misconfiguration from causing a complete meltdown.
This introduces a simple hierarchial structure that does not require any This introduces a simple hierarchial structure that does not require any
support code apart from in the nodes supporting the hierarchy. support code apart from in the nodes supporting the hierarchy.