home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 35 Internet
/
35-Internet.zip
/
tserve11.zip
/
TSERVE1.CFG
< prev
next >
Wrap
Text File
|
1996-01-24
|
10KB
|
233 lines
TSERVE1.CFG
This is a sample configuration file for the TSERVE program.
In fact, it's the very one I use on my first dial-in node!
Each parameter in this file begins with a parameter name which
includes a colon. That name must be the first thing on the line.
Everything after it on the same line is considered to be the
value of that parameter. If a line begins with something other
than a parameter name, the line is considered to be a comment.
The first thing to define for a TSERVE node is the COM port.
This can be any valid OS/2 port name. I use a digiboard and
reserve my lower com ports for SIO & VMODEM. You should put
your com port here.
PORT: com6
Next, specify the task number for this node. Each node must
have it's own unique task number and configuration file. It is
typical to use the same task number as would normally be the
maximus task number. However, this value will be stored as a
string so it is possible to use something other than a number
provided you find another way to give a unique task number to
maximus when it starts.
TASK: 1
Next, identify the fixed baud rate for the modem. This will be
passed to the PPP program, and is usually passed to maximus in
the -s command line option.
BAUD: 57600
Next, set up the modem initialization string. It is important
to set this string so that the modem will return result codes
in words, will return the callers connection baud rate, and
will not automatically answer the phone. The modem MUST return
the word RING when there is a caller. If your modem doesn't
return the caller's baud rate (ie. CONNECT 24000) then the
connect speed macro below (%C) will default to the locked rate.
This init string is for my Multi-tech ZDX modems. Note that the
M0 option keeps the modem from making a lot of noise when it's
negotiating a connection. If you prefer to hear the negotiation,
then leave the M0 out.
INIT: AT&FH0X1M0S0=0$SB57600X1$R1&E15
You'll probably want to use a more generic init string so you
might try this one...(TAKE THE SEMICOLON OUT OF THE FRONT OF
THE ONE YOU WANT TO USE AND PUT IT IN FRONT OF THE ONE YOU
DON'T WANT TO USE.)
; INIT: AT&FH0X1M0S0=0
Next, set up the default host IP address for this node. Each
TSERVER node that is running must have a unique IP address
within your domain. If you don't know what I mean by this, you
probably shouldn't be fiddling with this program! The default
host IP address can be over-ridden by a specific caller if
necessary, however it is typical to leave a node's HOST IP
address constant. It is also typical for this address to end
in something less than 10 as it is customary for routers to
have low IP addresses. You cannot use 0 as the final byte!
Replace the address below with your own host address!! DON'T
USE THE ADDRESS BELOW, IT IS ONLY AN EXAMPLE!
HOST: 206.239.24.3
Next, set up the default user IP address. This address will
usually be assigned to the caller when PPP establishes it's
connection with them. However, the default IP address can be
over-ridden by the user's record in the user file if it is
required. This would normally only happen if you wanted to
assign fixed IP addresses to remote callers.
Replace the address below with your own remote address!!
DON'T USE THE ADDRESS BELOW, IT IS ONLY AN EXAMPLE!
USER: 206.239.24.103
Next, set the idle timeout number. This value is usually
passed to the PPP program so that it can disconnect the user
after a period (in minutes) of inactivity. Unless you want
to allow people to connect and never leave, you must set and
use this option. I use a setting of 15 minutes which is long
enough for people to relax while browsing the web, but not
long enough for them to go on a lunch break and tie up the
line.
IDLE: 15
The last seven parameters relate to special macros. Each macro
represents one of the above parameters or a special message
from the tserver program. The following parameters are read
exactly as they are written until the end of the line, and
the macros are expanded without any additional leading or
trailing spaces. All macros begin with a % sign. If you wish
to have a % sign as part of your string then you need to
double it. For example, %P will expand to the port name from
the PORT: parameter above. %%P will expand to a % sign followed
by the capital letter P. The following is a list of the macros
which are available and their meanings.
%P Port name from PORT:
%O Open port handle.
%T Task number from TASK:
%H Host (Local) IP address.
%U User (Remote) IP address.
%B Fixed baud rate from BAUD:
%C Connect speed (read from the modem's connect message.)
%I Idle time from IDLE:
%L Login name entered by user.
%S Password entered by user (secret).
%K Current Time (clocK).
%A Current Date (cAlander).
%E Event string.. (Start, Connect, Close, Error,...)
It is very important to remember that these parameters must
fit onto one line. If the parameter is written on more than
one line, only the first line will be expanded. The remaining
lines will be ignored. It is best to use e.exe to edit these
files so that the lines can be as long as needed. However,
in practice, I've never had to edit a line much longer than the
usual 80 characters.
The next parameter to set is the name of the log file and it's
options. The log file can be left blank if no logging is
needed, however, it's a good idea to keep one around so that
you can find out about problems before a user has to tell you.
The first part of the parameter is the file name. It can be
any valid path and it can contain any of the expanding macros
from above. It is customary to use the task number %T in the
log file to distinguish it from others. The second part of
the log file parameter determines which events you want to
see stored in the file. This is done by including a list of
capital letters, each corresponding to a specific even that
you want included in the log file. These letters are:
B Begin,... When the program starts.
E End,... When the program ends.
R Ring,... when a ring is detected.
N No caller,... when a connection fails after RING.
L Login,... Reports the login code entered.
O No Login,... Reports when no login code is entered.
P Password,... Reports the password entered.
Q No Password,... Reports when reqd password not entered.
S Security,... Reports when a bad password is entered.
I Link,... Reports when PPP link started.
J End Link,... Reports when PPP link ended.
M Maximus,... Reports when BBS is started.
Z Z End,... Reports when BBS is ended.
X Xray,... Repoorts when an error occurs.
The following log file string works well for billing and most
trouble shooting. If you're really a glutton for punnishemnt,
turn them all on.
FILE: tserve%T.log
INCL: BLIJX
The next parameter tells tserver how to format the log entries
that are created. It produces the output you'll find in the
sample log.
LOGS: %A %K %L - %E
The next line is the file name of the user list. Please see the
documentation for the format of that file. The user list file can
be specified differently for each node, or set of nodes... It's
entirely up to you.
LIST: tserve.usr
The next two lines are file names for greeting and passing the user
to the BBS program. The HELO: file is what the user sees when they
first get connected.. This file should identify the system and maybe
the node, as well as give some instructions about how to proceed. If
you haven't registered your tserver package yet, this file will be
followed by a NAG message about the software being unregistered.
HELO: tserve.hlo
The POST: file is displayed after the tserver program determines that
the user is to be passed to the BBS system. It's really just there to
make the presentation more friendly to the user. If you don't need it
then leave it out or leave it blank.
POST: tserve.seg
The next two parameter lines really get the work done. The PPP: line
expands into the command line for starting a PPP link. The MAX: line
expands into the command line for starting a BBS session. It is
typical for the entire command line to be set in this file, but if
you really want to get experimental, you could make these lines call
external .CMD or .RXX files. I see no reason why it wouldn't work,
but it's not been tested and it's a lot more overhead.
The following PPP line is pretty vanilla and usually works. You can
get really fancy if you like and set up validation and other options
but it's probably not needed in most cases.
PPP: PPP %P %B mru 1500 rtscts %H:%U netmask 255.255.255.0 modem reneg priority 1 idle %I exit
The following BBS line is fairly reliable on multi-node maximus
systems. There is nothing to say that you couldn't put any program
here if you like. If you leave this line out, or leave it blank, then
tserver will end when a user puts in an unknown password or login
code.
Notice the "-j%L" parameter. This one lets maximus pick up as if the
user had already typed in their name (which they would have) giving
the appearance that maximus was answering the phone.
Notice also that the open port handle is passed to maximus with the
command line option -p%O. Maximus will not be happy about opening the
port by name, it must be passed a "hot" file handle. This is not the
case for the above PPP command since PPP will happily share a com
port that was opened in a share mode.
BBS: MAXP -p%O -n%T -s%B -b%C -ld:\max\max%T.log "-j%L"
That's really the end of the file. Of course, you should create your
own configuration files without all of the extra ramblings. If you
have any comments, or if you have an idea to improve the product,
please send e-mail to: peter.mcneil@micro-neil.com or if you'd like
to see this program in action, call the Think Pub at 703-406-8820.
Please report any bugs as well, and be as detailed as you can! We
don't think there are any bugs in here, but anything's possible.
Thanks!
More info about Micro-Neil and this product at http://www.micro-neil.com