You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all,
I'm planning to create an interface of Reticulum to software modems (like FreeDATA and Ardop), but most of these software modems just support point-to-point. Is there a problem of this in working with Reticulum?
Eg. of how a network operating in HF with UUCP works today: open a connection to host XX, sync the data, close connection, open a connection to host YY, sync the data, close connection... and so on. Is this model ok to work with Reticulum?
My plan is to use UUCP over Reticulum. Can anyone see a problem with it?
The text was updated successfully, but these errors were encountered:
There should not be any issues with this. Reticulum supports using any physical/virtual device as:
A point-to-point medium
A point-to-multipoint medium
A multipoint-to-multipoint medium (this one sounds weird, since it is so rarely used, but it is not a mistake)
Any of those can also have intermittency without causing problems (other than the syncing being unavailable sometimes, of course). You don't have to configure anything in these regards, Reticulum will figure it out automatically.
There are similarities to this in how LXMF works, so there should not be any problems as such.
Repository owner
locked and limited conversation to collaborators
Sep 28, 2022
Hi all,
I'm planning to create an interface of Reticulum to software modems (like FreeDATA and Ardop), but most of these software modems just support point-to-point. Is there a problem of this in working with Reticulum?
Eg. of how a network operating in HF with UUCP works today: open a connection to host XX, sync the data, close connection, open a connection to host YY, sync the data, close connection... and so on. Is this model ok to work with Reticulum?
My plan is to use UUCP over Reticulum. Can anyone see a problem with it?
The text was updated successfully, but these errors were encountered: