I did not see this on the roadmap, can we get support for connection scripts? Many packet connections will need to utilize either digipeaters or network nodes. Connections through network nodes require the ability to send commands to the node to establish the connection. This support is in Winlink Express and WoAD.
-Scott, NS7C
Is there a good reference for these kind of scripts? What commands they issue and when they need to be executed? I'm not familiar enough with digipeating and never heard of network nodes, so I need to learn.
Digipeating is not supported in RadioMail at the moment and I don't have access to any locally so for this to be considered I would need a solid spec to start from and some volunteers to test it out.
The simplest description is in the Winlink Express help file, I will attach the specific section. The scripts are free form, since the actually commands needed vary between the different types of nodes. Digipeating is rather different than using a node, but a similar concept. I have access to all of the above and would be happy to beat to death anything you want to test.
-Scott, NS7C
Packet connections.pdf (64.1 KB)
Thanks. At cursory look seems that scripts are for network nodes only not digipeaters is my understanding correct?
That is correct. Digipeater connections are simple "connect via" sessions where all packets are relayed through an intermediate station (in both directions). The digipeater does not process the packets at all, it just forwards them on. You do not "connect" to a digipeater. You do connect to network nodes, and then issue commands to the network node to connect to other stations (or nodes) to establish an end-to-end connection.
Attached are the specifications for digipeaters in the AX.25 protocol.
-Scott, NS7C
The Layer 2 digipeater.pdf (83.8 KB)
Looking at script syntax, is there a functional difference between `!WAITFOR text` and putting a response text that would be provided after the `CONNECT xxx` command?
Also, Winlink Express expects an even number of connection/response. WoAD mention that "The final connection request is assumed to terminate at either a Winlink CMS or P2P server, for which no response line is necessary." which seems to indicate that the script could end on a `CONNECT xxx` command. So I'm inclined to not enforce the "evenness" of the connect/response.
RadioMail 1.3.3 now supports packet node connection scripts. https://radiomail.app/help/packet#script