Subj : Re: Question About FTN Hubs
To   : Lord Gareth
From : Vk3jed
Date : Fri Jun 05 2020 20:21:00

-=> On 06-04-20 23:24, Lord Gareth wrote to Vk3jed <=-

 LG> So the node list is manually updated every week?

Entries are made manually, but I have a set of automated scripts that process
and distribute the nodelist every week.  All I have to do is add, delete or
modify entries in the master file as needed, and the automation does the rest.
:)

 LG> Also, how does the hub/node relationship work overall?  When you start
 LG> a new network/hub do you set your settings up as a Node instead of as
 LG> an echomail net in Mystic's settings?  Also, how do you go about

This question confuses me, I'm not sure what you mean.  FTN is really peer -
peer, it's just a matter of who polls who, at a link level.  

 LG> assigning nodes?  Is it just a matter of assigning an open number
 LG> between 001-999 as the node address to the individual requesting access
 LG> and then adding them to the node list for the next refresh?

Pretty much. :)

 LG> I think that makes sense.
 LG> So to start a net, you need to find an open network address (IE 21 for
 LG> fsx), you then pick your hub address, usually 1 for the first hub, and
 LG> then a node considered to be the base node, usually 100 from what I

Pretty much, though for one net, I picked 8 as the first net, because it fitted
the overall theme of the net.  You don't have to start with Net 1.

 LG> see.  You set that up as the node settings and as the echomail net
 LG> because, well, you are the node and the net.  When someone wants to
 LG> join your net, you assign them a node number which will connect back to
 LG> you and allow you to communicate back out to them and other members of
 LG> the net.  You add that new person to your node list.

When you add a node, you have to:

1.  assign a node number and add it to the nodelist.
2.  Assign passwords (having an application form allows the prospective node to
choose those).
3.  Configure the node in your tosser and mailer (in Mystic, in Echomail
odes).

At this point, it should be possible to poll, and then the node can use Areafix
and Filefix to connect their chosen message and file echos.

 LG> But, I don't know how the TIC/Areafix/Filefix stuff comes into play.
 LG> How do you set up those pieces for the new node owner?  What does it
 LG> authenticate against on your BinkP server?

Authentication against binkp is done using the session password.

Areafix allows the other node to tuen on and off message areas.
Filefix does the same for files.

Allfix (or "Fix" in Mystic") just means that the Areafix and Filefix passwords
are configured as one (and are the same).

TIC is the mechanism that is used for the file echos.  a TIC file describes the
file to be distributed and the echo in which it is being distributed in.  It
also contains a number of technical details and some directives.


.... Gravity doesn`t exist: the earth sucks.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
 * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

.