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.EX1
< prev
next >
Wrap
Text File
|
1992-06-25
|
4KB
|
92 lines
The Scenario:
David and I live in Toronto and James lives in Vancouver. All
three of us want to be able to link our boards together so that we can play
against each other. I call James for mail on a daily basis, so it's easy
for me to route the game files between our three boards. This way, only
one of us pays long distance charges instead of all three of us calling
each other whenever there are new game files to be transferred. We all
have a valid SigNet Address, so this is the address that we will be using
in our ROUTE.CFG files (Remember, the Address listed in your ROUTE.CFG file
can be ANY Valid address that you have and does not have to be the address
that you have configured in your ISA.CFG) The Following ROUTE.CFG files
would be used:
David will be sending game files to me, and he will be routing
game files destined for James through my system as well. David's address
is 34:2416/10. He will need to send the files to my address at 34:3416/0
as well he needs to configure James' address 25:4604/171
David's ROUTE.CFG would look like this:
--------------------- CUT HERE -----------------------
*34:2416/10
%34:3416/0
#N
?34:3416/0
?25:4604/171
--------------------- CUT HERE -----------------------
Since we are all using our SigNet addresses, David configures ISA to
use his 34:2416/10 address (as indicated by the '*' operator).
He sends the game files to me at my SigNet address as indicated by the
'%' operator.
The '#N' indicates that David wishes to use a Normal flag on the file
attach messages so as not to override any Temporary Event Mail Hold's that
he has set up.
Notice the two '?' operators listed. This tells ISA that files for
34:3416/0 and 25:4604/171 should BOTH be sent to 34:3416/0.
Since I will be the 'Hub' or pass-through system for David and James,
I need to configure my routing file to ensure that files destined for
either of their systems get sent to the right place. My ROUTE.CFG file
would look like this:
--------------------- CUT HERE -----------------------
*34:3416/0
%34:2416/10
#N
?34:2416/10
*34:3416/0
%25:4604/171
#N
?25:4604/171
--------------------- CUT HERE -----------------------
Notice that the 4-Line command block is duplicated. Since I feed
both systems with game files, I create one 4-Line command block for each
system. This way any game files that come in from James' system get sent
to David, and any files that come in from David's system get redirected to
James's system.
To complete this example, James' ROUTE.CFG will be almost identical
to David's. The only changes will be that James will insert his Address in
the '*' operator and David's address as the second '?' operator. James'
ROUTE.CFG would look like this:
--------------------- CUT HERE -----------------------
*25:4606/171
%34:3416/0
#H
?34:3416/0
?34:2416/10
--------------------- CUT HERE -----------------------
Notice the one other difference between James' and David's ROUTE.CFG
files is that James uses the Hold flag instead of the Normal flag. Since I
call James, he can put the files on Hold to prevent his system from calling
me since I will call his system anyway.
Hopefully this will clear up any confusion you may have had in
regards to routing files. If you are comfortable with this and want to see
how the ROUTE.CFG files would look in a larger installation, move on to the
file ROUTE.EX2.
If you are still totally confused, or are having problems
implementing file Routing, feel free to contact me at:
Jeff Bolton on Scruples! (416)661-5426 AdultNet 15:15/1
FidoNet 1:250/517
SigNet 34:3416/0