LyqydNet-related modem protocols#
From 2012 to 2017, Lyqyd has made a set of network solutions using a common set of solutions named “LyqydNet”, notably used in CC-Hive.
Todo
Similarities with Rednet, e.g. using computer IDs (with limits!). What ports is it using? Not actually sure
Dissimilarities with Rednet, e.g. no repeat port, etc.
Transport AND application protocol… bad, really.
See the main repository and the net daemon source code for more information.
Packet format#
Packets are tables containing the following fields:
Attribute |
Presence |
Role |
---|---|---|
|
Required |
Always set to |
|
Required |
Set to the destination host’s numerical computer identifier. |
|
Required? |
Set to the source host’s numerical computer identifier. |
|
Required. |
Set to a two-character identifier for the packet’s purpose. |
|
? |
A numerical identifier of the destination socket (equivalent to a “port” in more traditional connected transport protocols). |
|
? |
A numerical identifier of the source socket (equivalent to a “port” in more traditional connected transport protocols). |
|
? |
An acknowledgement request flag which makes the current
host repeat the message to the sender with the |
Packet types are the following:
Code |
Family |
Role |
---|---|---|
|
Socket |
A query? |
|
Socket |
A response? |
|
Socket |
A data packet? |
|
Socket |
An instruction? |
|
Socket |
“done”? |
|
Socket |
“close”? |
|
Packet |
A packet acknowledgement, or “packet success”,
returning on |
|
Hosts |
Add a host route? |
|
Hosts |
Send a hosts table? |
|
Hosts |
A host sends its own information. |
|
Hosts |
A host saves a Cost? |
|
Hosts |
Broadcasting |
|
Hosts |
Remove a route. |
|
Rednet |
A Rednet message to be treated as Rednet message? |
Socket instruction (SI
) packet payloads are the following:
Code |
Role |
---|---|
|
Announce ourselves as |
|
? |
|
Enable routing? |
|
Enable longlink mode? |
|
? |