home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-385-Vol-1of3.iso
/
i
/
isa_099.zip
/
ISAROUTE.ZIP
/
ROUTE.DOC
next >
Wrap
Text File
|
1992-06-15
|
5KB
|
99 lines
╔═════════════════╗
║█▓▒░ Routing ░▒▓█║
╚═════════════════╝
ISA now supports file routing. This will allow you to route game
files through a 'hub system' to other systems (possibly out of town), vastly
increasing the number of systems you can play against. If you are familiar
with the concept of Echomail, you should have a good idea of how this
feature will accomplish this task.
ISA reads it's routing information from the file ROUTE.CFG. This
file MUST be created in your ISA Game Directory for the routing to work.
The routing file recognizes four (4) command characters. The format of
the file is as follows:
*<The address ISA should use when generating the Netmail Attach message>
%<The address of the HUB you will be sending the mail to>
#<The netmail status flag - C,H,I,N for Crash, Hold, Immediate and Normal>
?<The address of all systems to be routed through the HUB listed above>
Let's take a look at each of these in a little more detail.
* The '*' operator indicates the Net Address that ISA should use when
sending out mail. This does not have to be the same address that you
have in your ISA.CFG file. This allows ISA to use multiple network zone
addresses to permit you to play against other systems which use a different
zone based address than your system does. The address you use here can be
any Valid address or aka address that your system currently has.
Example:
I participate in 3 seperate networks, thus I can place any of my
three addresses on this line.
*15:15/1 - I use this address to send to other AdultNet systems.
*1:250/517 - I use this address to send to other FidoNet systems.
*34:3416/0 - I use this address to send to other SigNet systems.
% The '%' operator indicates the Net Address of the 'HUB' that I wish to
route game files through. ISA will send game files originating on my
system to this address, who in turn will pass the files along to their
destination.
Example:
I want to route files through James' system to Eddie. Since James
is the 'HUB' for this routing, I enter James' address on this line.
%25:4604/171
# The '#' operator works the same here as it does in your NODES.CTL
file. The valid parameters are C,H,I,N for Crash, Hold, Immediate
and Normal. I strongly recommend NOT using Crash or Immediate in the
ROUTE.CFG as these may interfere with the normal routing commands that
your mailer may be using. If you call the 'HUB' system, use the Normal
flag, or if the 'HUB' calls you, use the Hold setting.
Example:
I call James' system to deliver/pickup game files daily, in this
case I would use the Normal flag.
#N
? The '?' operator instructs ISA as to which systems' game files are to
be routed through the address listed above with the '%' operator.
This may seem a little strange, but the FIRST instance of this operator
MUST be the same address as indicated by the '%' operator listed above.
This operator may be repeated as many times as needed to include all
systems that you route through the specified 'HUB' system.
Example:
I route files for Eddie's system through James. I will need to
have two '?' operators here to specify that I will be routing to James'
system and to Eddie's system.
?25:4604/171
?25:4604/139
In addition to the above, you will have to add each system that you
will be routing files for to your NODES.CTL file. The procedure for adding
new nodes is described earlier in this documentation. Although the files
for these systems will be routed, you still treat them as if you were calling
directly to the nodes yourself in terms of setting them up in your NODES.CTL
file.
To clarify things even further, I have included a couple of well
documented Sample routing files that you can study/modify to suit your
needs. These files have been tested and work as they were intended on my
BBS. ROUTE.EX1 is a simple routing engagement involving 2 'End' systems
and one 'Hub', whereas ROUTE.EX2 is a little more complicated and involves
several systems.
NOTE: If a file is routed and the destination or pass-through system
is not listed in the ROUTE.CFG file, the file will NOT be forwarded and it
will be used by ISA on your BBS. This can cause attacks intended for
another BBS to end up on your BBS attacking the wrong person. Do not set
up your ROUTE.CFG to forward files until you have checked with your uplink
and they are ready to forward the file on to the proper destination.