home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
HAM Radio 1
/
HamRadio.cdr
/
packet
/
bb211
/
fwd.doc
< prev
next >
Wrap
Text File
|
1991-02-09
|
9KB
|
248 lines
To forward to a station, that station must now be designated a BBS or a
personal BBS. Use the EU command and set the proper flag.
B flag -- Old BBS programs that don't have the [xxx] info
A flag -- Advanced BBS that does send [xxx]. When in doubt,
use this flag
P flag -- Personal BBS.
Rather than the current way of having a list of destinations for each
route, a list of routes for each destination is used. The data has been
broken into two pieces. How to connect with a distant mailbox is in the
PATH file while the information on what to send is in the ROUTE file.
The ROUTE File
--------------
A line from the ROUTE file is organized as:
W3IWI W0RLI WB6ASR 80 KE6BX
This says to send mail for W3IWI mailbox down the path named either
W0RLI, WB6ASR, and then KE6BX. The forwarding will be performed in that
order. W0RLI will be tried first and then WB6ASR. If a message is
more than 80 hours old, KE6BX will be used.
Wildcards are supported. For full details on these, see WILDCARD.DOC.
Just more than * is supported.
Once a message (or a member of a distribution list has been selected, it
cannot be selected for another route.
95020 AA4RE
95* W0RLI
A message with a route code of 95020 will go to AA4RE. All others go to
W0RLI. 95020 will not since it was selected for the AA4RE route already.
The ROUTE files also allows ALIASES. These are of the form
SOCAL = K6IYK W6PW
Anywhere SOCAL appears in a route, K6IYK W6PW will be substituted. So
if the ROUTE file says
WB6YMH SOCAL
this is the same as
WB6YMH K6IYK W6PW
Aliases only affect the path to use. Aliases must be listed before they
can be used.
>>> Special cases:
If you send something to LEAVE then it will stay on the BBS and not
be forwarded. This is handy to prevent just certain messages to stay.
Example:
95020 LEAVE
95* KE6BX
A message to 95020 will stay but all other 95anything will go to
KE6BX.
If the special @BLANK is used, this will match any message where
the @BBS field is blank. Combining LEAVE and BLANK make some
route tables easy:
AA4RE LEAVE
@BLANK LEAVE
* WB6ZVW
Any message addressed to @AA4RE stays. Any message addressed to
anycall without @ will stay. All others will go to WB6ZVW. This
is very handy for a small BBS where everything but local calls go
to one other BBS.
If you send something to ? then it will stay on the BBS and not
be forwarded. It will show up if you execute the L? command.
Example:
USA ?
A message to USA will be marked with the ? flag
The PATH File
-------------
The PATH file has the entries that describe how to connect to a
mailbox we want to forward to. A typical entry:
PATH W0RLI B W0RLI
O TA
T 0000 0600
T 1000 1600 1 5
T 2200 2359
C W6AMT-10
PF 12
SC #SFO3
R* to *
SC SNTCRZ
R* to *
SC W0RLI
R* to *
PATH pathname port callsign force
"pathname" is the name of this path. Any arbitrary 12
characters will do. This matches the entry in the
ROUTE file.
"port" is the letter of the port to use to connect to this
mailbox on. If this is a DRSI card, you must also code the
port on the C(onnect) statement.
"callsign" is used to set certain parameters found in the USER file
(like MAXPAC etc). Any call can be used here as long as the USER
file contains the information. This call is also used for REVERSE
FORWARDING.
"FORCE" -- If the actual word FORCE appears after the
callsign, connect via this path even if no messages.
C(onnect) callsign
This is the actual connect command to be used. For the
DRSI card, don't forget to include port. Example:
C 1:AA4RE
P(ort) cmd
This is a command to be issued to this port. Can be
used to change all sorts of things. Be careful to affect
only this "channel". See the documentation for your TNC
as to what is allowed.
S(end) text
Send the text of this line to the distant station.
R(ecieve) pattern
If the next line received from the distant station does not
match this line disconnect. Full pattern matching can be used.
"R* to *" is great for the NETROM response. Be careful when
constructing your own pattern. It starts immediately after the
"R" without an intervening blank.
O(Order) order_info
This controls how messages are ordered before forwarding.
order_info can have up to three characters:
A -- Order by age with oldest first
T -- Order by type. T before P before B. This is
actually an alphabetical sort. Special case
of "P" with distribution list is same as "B"
S -- Order by size. Smallest first
D -- Order by day. Similar to A but only the day matters
and not the time. Oldest first.
R -- Reverse of D. Latest is first.
If you code the letters TA then the messages will be sent
by type then age within type. Thus the first message sent
will be the oldest "T" message. The order will look
like this:
oldest "T" message
.
newest "T" message
oldest "P" message
.
newest "P" message
oldest "B" message
.
newest "B" message
Note that using "A" as a parameter except as the last letter
is kinda useless. If you gave "AT" then messages would be
ordered by AGE then type. The probability of two messages
being the same AGE (down to the second) is very very small.
This is why the "D" is given. "DT" would order by DAY and
then TYPE within DAY.
Note 1: The "O" statement must be before any "C" statements
Note 2: There is a DEFAULT_FORWARD_ORDER parameter that
applies on a port basis in PARMS.BB
T(ime) start_time end_time start_day_of_week end_day_of_week ...options...
Use this path during certain times.
start_time = start time we can use path. HHMM format
stop_time = stop time we can use path. If not given then
we can forward anytime after start time.
start_day_of_week = Day of week we can use this path.
Sunday = 0, Monday = 1, etc. If omitted, can
use any day. If no end_day_of_week given then
path can be used this day ONLY.
end_day_of_week = Last day path can be used.
options = options for more control.
HOUR x/y If the hour divided by x has a
remainder of y then forward.
Examples:
HOUR 2/0 Only even hours
HOUR 2/1 Only odd hours
HOUR 3/1 Every 3 hrs (0100 is ok)
ORDER ccc Same as "O" but only for this time
period. Must be last thing on line.
SIZE nnn Max size to forward in this time period
Note 1: All start/end are INCLUSIVE.
Note 2: You can have many "T" statements. If ANY of them
is true, you can forward.
Note 3: The "T" statement must be before any "C" statements
Note 4: The ORDER operand will be wiped out by an "O" statement
so put "O" statements before "T"
Examples
T 0900 2300 Use this path from 0900 to 2300
T 0000 2359 1 5 Use this path from Mon to Fri
T 0000 2359 0 6 HOUR 2/0 Any day but only even hours
T 0000 0800 6 6 HOUR 2/1 Odd hours between midnight and
eight AM on saturday only
T 1200 2359 0 6 ORDER DT Forward between noon and midnight
on any day with order sequence DT
T 1200 2200 0 6 SIZE 100 Forward between noon and 10 PM
on any day but only messages of 100
bytes or less
T 1200 2359 0 6 ORDER DT SIZE 100
Forward between noon and midnight
on any day with order sequence DT
but only messages of 100 bytes or
less
***** NOTE *****
To ensure proper operation, execute the GF command after updating
ROUTE.BB