<metaname="description"content="FidoNet-Style Networks (FTN) FidoNet proper and other FidoNet-Style networks are supported by ENiGMA½. A bit of configuration and you’ll be up and running in no time!"/>
<metaproperty="og:description"content="FidoNet-Style Networks (FTN) FidoNet proper and other FidoNet-Style networks are supported by ENiGMA½. A bit of configuration and you’ll be up and running in no time!"/>
{"publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"/enigma-bbs/assets/images/enigma-logo.png"}},"description":"FidoNet-Style Networks (FTN) FidoNet proper and other FidoNet-Style networks are supported by ENiGMA½. A bit of configuration and you’ll be up and running in no time!","url":"/enigma-bbs/messageareas/ftn.html","@type":"BlogPosting","headline":"FidoNet-Style Networks (FTN)","dateModified":"2022-04-07T18:25:24+00:00","datePublished":"2022-04-07T18:25:24+00:00","mainEntityOfPage":{"@type":"WebPage","@id":"/enigma-bbs/messageareas/ftn.html"},"@context":"https://schema.org"}</script>
<p><ahref="https://en.wikipedia.org/wiki/FidoNet">FidoNet</a> proper and other FidoNet-Style networks are supported by ENiGMA½. A bit of configuration and you’ll be up and running in no time!</p>
<p><imgclass="emoji"title=":scroll:"alt=":scroll:"src="https://github.githubassets.com/images/icons/emoji/unicode/1f4dc.png"height="20"width="20"> Before proceeding you may wish to check <ahref="https://medium.com/@alpha_11845/setting-up-ftn-style-message-networks-with-enigma%C2%BD-bbs-709b22a1ae0d">Setting up FTN-style message networks with ENiGMA½ BBS</a> by Alpha. An excellent guide detailing some of the setup described here!</p>
<h3id="configuration">Configuration</h3>
<p>Getting a fully running FTN enabled system requires a few configuration points:</p>
<ol>
<li>
<codeclass="language-plaintext highlighter-rouge">messageNetworks.ftn.networks</code>: Declares available networks. That is, networks you wish to sync up with.</li>
<li>
<codeclass="language-plaintext highlighter-rouge">messageNetworks.ftn.areas</code>: Establishes local area mappings (ENiGMA½ to/from FTN area tags) and per-area specific configurations.</li>
<li>
<codeclass="language-plaintext highlighter-rouge">scannerTossers.ftn_bso</code>: General configuration for the scanner/tosser (import/export) process. This is also where we configure per-node (uplink) settings.</li>
</ol>
<p><imgclass="emoji"title=":information_source:"alt=":information_source:"src="https://github.githubassets.com/images/icons/emoji/unicode/2139.png"height="20"width="20"> ENiGMA½’s <codeclass="language-plaintext highlighter-rouge">ftn_bso</code> module is <strong>not a mailer</strong> and makes <strong>no attempts</strong> to perform packet transport! An external utility such as Binkd is required for this task.</p>
<h4id="networks">Networks</h4>
<p>The <codeclass="language-plaintext highlighter-rouge">networks</code> block is a per-network configuration where each entry’s ID (or “key”) may be referenced elsewhere in <codeclass="language-plaintext highlighter-rouge">config.hjson</code>. For example, consider two networks: ArakNet (<codeclass="language-plaintext highlighter-rouge">araknet</code>) and fsxNet (<codeclass="language-plaintext highlighter-rouge">fsxnet</code>):</p>
<pre><codeclass="language-hjson">{
messageNetworks: {
ftn: {
networks: {
// it is recommended to use lowercase network tags
fsxnet: {
defaultZone: 21
localAddress: "21:1/121"
}
araknet: {
defaultZone: 10
localAddress: "10:101/9"
}
}
}
}
}
</code></pre>
<h4id="areas">Areas</h4>
<p>The <codeclass="language-plaintext highlighter-rouge">areas</code> section describes a mapping of local <strong>area tags</strong> configured in your <codeclass="language-plaintext highlighter-rouge">messageConferences</code> (see <ahref="/enigma-bbs/messageareas/configuring-a-message-area.html">Configuring a Message Area</a>) to a message network (described above), a FTN specific area tag, and remote uplink address(s). This section can be thought of similar to the <em>AREAS.BBS</em> file used by other BBS packages.</p>
<p>When ENiGMA½ imports messages, they will be placed in the local area that matches key under <codeclass="language-plaintext highlighter-rouge">areas</code> while exported messages will be sent to the relevant <codeclass="language-plaintext highlighter-rouge">network</code>.</p>
<td>An array of FTN address uplink(s) for this network</td>
</tr>
</tbody>
</table>
<p>Example:</p>
<pre><codeclass="language-hjson">{
messageNetworks: {
ftn: {
areas: {
// it is recommended to use lowercase area tags
fsx_general: // *local* tag found within messageConferences
network: fsxnet // that we are mapping to this network
tag: FSX_GEN // ...and this remote FTN-specific tag
uplinks: [ "21:1/100" ] // a single string also allowed here
}
}
}
}
}
</code></pre>
<p><imgclass="emoji"title=":bulb:"alt=":bulb:"src="https://github.githubassets.com/images/icons/emoji/unicode/1f4a1.png"height="20"width="20"> You can import <codeclass="language-plaintext highlighter-rouge">AREAS.BBS</code> or FTN style <codeclass="language-plaintext highlighter-rouge">.NA</code> files using <ahref="/enigma-bbs/admin/oputil.html">oputil</a>!</p>
<h4id="a-more-complete-example">A More Complete Example</h4>
<p>Below is a more complete <em>example</em> illustrating some of the concepts above:</p>
<pre><codeclass="language-hjson">{
messageNetworks: {
ftn: {
networks: {
fsxnet: {
defaultZone: 21
localAddress: "21:1/121"
}
}
areas: {
fsx_general: {
network: fsxnet
// ie as found in your info packs .NA file
tag: FSX_GEN
uplinks: [ "21:1/100" ]
}
}
}
}
}
</code></pre>
<p><imgclass="emoji"title=":information_source:"alt=":information_source:"src="https://github.githubassets.com/images/icons/emoji/unicode/2139.png"height="20"width="20"> Remember for a complete FTN experience, you’ll probably also want to configure <ahref="/enigma-bbs/messageareas/bso-import-export.html">FTN/BSO scanner/tosser</a> settings.</p>
