Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| howto:freq [2021/03/19 09:36] – updated examples to use paths for the req and flo files wkitty42 | howto:freq [2021/03/19 10:24] – a little refinement wkitty42 | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| This page describes how to create a FTN style FREQ (FileREQ) and send it to a destination system. There are at least two methods this can be done with. Currently we will describe only one of those methods. | This page describes how to create a FTN style FREQ (FileREQ) and send it to a destination system. There are at least two methods this can be done with. Currently we will describe only one of those methods. | ||
| - | The first step is to create a .req file. This file contains the filenames of the files you are requesting, one filename per line. | + | The first step is to create a .req (REQuest) |
| eg:< | eg:< | ||
| echo anotherfile.bar >> / | echo anotherfile.bar >> / | ||
| - | Now that we have the filenames in a .req file, we want to send it to a destination system. One way this is done is to add myfreq.req to a .FLO file. This requires some understanding of how BSO (Binkley Style Outbound) works so we can determine the proper FLO file name of the destination system. Basically, the zone is determined by the outbound directory in your BSO tree. The net and node of the destination are zero-padded HEX to four places. | + | Now that we have the filenames in a .req file, we want to send it to a destination system. One way this is done is to add myfreq.req to a .FLO file. This requires some understanding of how BSO (Binkley Style Outbound) works so we can determine the proper FLO file name of the destination system. Basically, the zone is determined by the outbound directory in your BSO tree. The outbound directory for your default zone has no extension. The extensions on your other outbound directories are zero-padded HEX to three places. The net and node of the destination are zero-padded HEX to four places. |
| eg: 1:3634/12 breaks down like this. | eg: 1:3634/12 breaks down like this. | ||
| - | < | + | < |
| + | the net 3634 : 0e32 | ||
| the node 12 : 000c</ | the node 12 : 000c</ | ||
| Line 19: | Line 20: | ||
| < | < | ||
| - | |||
| - | The ' | ||
| If our default zone is not zone fidonet zone 1, then the outbound directory will be outbound.001 and we'd create our flo file there. | If our default zone is not zone fidonet zone 1, then the outbound directory will be outbound.001 and we'd create our flo file there. | ||
| Line 26: | Line 25: | ||
| < | < | ||
| - | When your BSO mailer scans out outbound directories and sees the file 0232000c.flo, it will attempt to connect to 1:3634/12 and deliver the myfreq.req file. If 1:3634/12 has FREQ enabled, it will read the filenames from the .req file and queue them to send back to you during the current connection. | + | Let's say we want to send a FREQ to a system in Micronet. Micronet is zone 618. In HEX that is 26a so the outbound would be outbound.26a. So, a request to 618:3634/12 would look like this. |
| + | |||
| + | < | ||
| + | |||
| + | When your BSO mailer scans its outbound directories and sees the file 0e32000c.flo, it will attempt to connect to 1:3634/12 and deliver the myfreq.req file. If 1:3634/12 has FREQ enabled, it will read the filenames from the .req file, and queue those files to send back to you during the current connection. | ||
| + | |||
| + | |||
| + | NOTES: | ||
| + | The ' | ||
| In the above you will note that we used the ">>" | In the above you will note that we used the ">>" | ||
