bbs/deb-mbse
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated documentation

Browse Source
This commit is contained in:
Michiel Broek 2001-12-29 15:17:18 +00:00
parent 2f53919c93
commit 86a46d24fd
10 changed files with 206 additions and 174 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
html/basic.html
View File

@ -11,7 +11,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 25-Dec-2001</h5>
<h5>Last update 29-Dec-2001</h5>
<P>&nbsp;<P>
<h1>MBSE BBS Basic Installation</h1>
@ -82,6 +82,8 @@ this error.
<h3>Step 2: Running the installation script.</h3>
<p>
If you are upgrading, proceed with step 4. If not, follow the next steps
very carefully!
The installation script must be run by root. It checks if there is a
previous or failed installation on your system. If that's so the script will
not run. In other words, you can only run this script once. The script makes
@ -164,7 +166,9 @@ will not be installed again.
Now you must start the <b>mbtask</b> daemon by hand by typing <b>/opt/mbse/bin/mbtask</b>.
Check the file <b>/opt/mbse/log/mbtask.log</b> for startup problems. You may notice that
the program <b>mbcico</b> is started everytime, this is not a problem, it simply doesn't work right
now because you haven't configured anything yet.
now because you haven't configured anything yet. The first time <b>mbtask</b> is
started on your system it will create a lot of new configuration files with
default settings.
<p>&nbsp;<p>
<h3>Step 5: (RedHat) startup problems.</h3>

19
html/dist.html
View File

@ -11,16 +11,18 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 06-Jun-2001</h5>
<h5>Last update 29-Dec-2001</h5>
<P>&nbsp;<P>
<H1>Linux Distributions.</H1>
<H1>Unix Distributions.</H1>
<P>
<H3>Which distribution</H3>
<P>
Linux is available in several distributions, they all have advantages and
disadvantages for bbs use. Which distribution to pick is very personal.
Since late 2001 a port to FreeBSD is available, from version 0.33.19 this
port is ready to use.
You should also consider the fact if the bbs machine is the same machine on
which you do your daily work on or if you use a seperate system for the bbs.
I will describe the distributions below for use on dedicated bbs computers,
@ -60,6 +62,17 @@ The installation works on a Debian 2.1 and 2.2 distribution without any problems
How to build an optimized Debian system is not tested by me.
<P>&nbsp;<P>
<H3>FreeBSD</H3>
<P>
I test on a FreeBSD 3.2 stable release. Newer releases will not run on the
hardware I have available. (Don't ask me why, they crash during install).
The setup is quite simple, do a small setup (average user), and add some needed packages
from the ports collection such as gcc, mgetty, infozip etc. The test machine
has a 500 MB harddisk, about 250 MB is still free. Note that the older
precompiled mgetty packages may not always have Fidonet support compiled in.
You may need to build mgetty yourself if you have an older FreeBSD distribution.
<P>&nbsp;<P>
<H3>Famous last words...</H3>
<P>
I don't have the diskspace for all kinds of Linux distributions to install
@ -68,7 +81,7 @@ installed. Also, I don't buy every new distro that's available. If you have
a problem with that, just send me the new distro on CD to test by snailmail.
<P>&nbsp;<P>
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back" border="0"> Go Back</A>
</BODY>
</HTML>

33
html/flow.html
View File

@ -6,21 +6,21 @@
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>Running a BBS under Linux.</TITLE>
<TITLE>Running a BBS under Unix.</TITLE>
<LINK rel=stylesheet HREF="manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 06-Jun-2001</h5>
<h5>Last update 29-Dec-2001</h5>
<P>&nbsp;<P>
<H1>Running a BBS under Linux.</H1>
<H1>Running a BBS under Unix.</H1>
<P>
<h3>Introduction</H3>
<P>
Everyone who has been running a (single line) BBS under DOS until now will
need to understand that running a BBS under Linux (or any other multitasking
need to understand that running a BBS under Unix (or any other multitasking
os) is completly different of what you are used to. Under DOS things were
quite simple, from AUTOEXEC.BAT you started a new .BAT file that would run
forever and started all needed programs after each other.
@ -33,7 +33,7 @@ a BBS on a small lan with a fileserver and workstations for each line, are
already more used to the idea of running more programs at the same time,
and to "signal" what to do next with semafore files.
<P>
The Linux aproach is more or less the same, but there are more differences.
The Unix aproach is more or less the same, but there are more differences.
The main difference is that there is no mailer connected with the modem waiting
for a call, instead there is a getty process watching your modem(s). Another
big difference is that you don't see what's happening, there is no screen
@ -42,16 +42,17 @@ you don't like that, stop now and go back to your old DOS bbs. It's just the
way everything is done.
<P>
Programs that must start at specific times (events in DOS), are started from
cron, this is the event scheduler for Linux (and other Unixes). With this
cron, this is the event scheduler for Unix. With this
program maintenance can be started, polls created etc. For starting programs
when they are needed there is a taskmanager loaded at system bootup. This
taskmanager "watches" the semafore directory of the bbs and will start what
is needed.
is needed. It will also watch the mailer outbound to see if there are nodes
to call.
<P>&nbsp;<P>
<H3>Waiting for a call .....</H3>
<P>
Under Linux this is done with the mgetty program, this is the
Under Unix this is done with the mgetty program, this is the
process that is connected with each modem (or ISDN adapter) and waits for a
call. The mgetty program (written by Gert Doering, gert@greenie.muc.de) will
detect the call, and find out what or who did make the call. It can detect
@ -65,14 +66,14 @@ installation manuals, but be sure to compile it with Fido and PPP support.
<H3>A Human is calling.</H3>
<P>
This could be a bbs user. For each user to login to your bbs there must be a
This could be a bbs user. For each user to login to your bbs there is a
unix account. They automatic create such an account the first time they login
with the <b>bbs</b> account. During the creation of their account the shell that is
installed for there account is the mbsebbs binary, so that's the only thing
that they get if they call in. When they logout the bbs, or drop carrier etc,
the session is ended and mgetty takes over the line again.
Note that they will never can get a Unix shell
unless you install a <b>door</b> in the bbs that calls a shell for them.
Note that they never can get a Unix shell unless you install a <b>door</b>
in the bbs that calls a shell for them.
<P>
There are probably more accounts on your system that can callin, <b>mbse</b> is
such an account, this is the MBSE BBS maintenance account. This user will
@ -98,8 +99,7 @@ take over from mgetty. It will establish a mail session with the caller and
the mail and or files will be exchanged just like any DOS mailer would do.
After the call, mbcico will hangup and mgetty will take control of your modem
again. If there is any mail received, mbcico will place the semafore <b>mailin</b>
so that another process can take care of the received mail. Mbcico will also
detect some IEMSI terminal programs (Frontdoor), and will start the bbs.
so that another process can take care of the received mail.
<P>&nbsp;<P>
<h3>There is mail in the inbound</h3>
@ -131,7 +131,10 @@ mails too. Note that other crashmails are send anytime. Also note that packed
mail and files are not send during ZMH. If a node calls you during ZMH he will
get everything that's waiting, including packed mail and files. The task manager
(more on that later) calculates the Zone Mail Hour from UTC time, you don't
have to change anything for summer- and wintertime.
have to change anything for summer- and wintertime. The taskmanager knows about
all zone mail hours of all Fidonet zones (1..6). For othernets, zone mail hour
is taken from the setup as default value. The taskmanager will also handle the
mail for nodes with the Txx flag (FSC-0062) on the right times.
<P>&nbsp;<P>
<H3>Daily maintenane</h3>
@ -145,7 +148,7 @@ I have made several scripts for this, daily, weekly and monthly.
<P>
Because Linux is a 32 bit os, not bothered with a graphical user interface
(unless you install it), it has all the time in the world to serve your
bbs programs. Background programs are build to release time to the Linux os,
bbs programs. Background programs are build to release time to the Unix os,
they don't need to run fast because it's background processing. The bbs and
the mailer, have a low server load although there is no timerelease build
in. Only the bbs has some short moments when it needs a lot of your system,

BIN
html/images/tty.gif
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 9.8 KiB

After

Width:  |  Height:  |  Size: 12 KiB

BIN
html/images/tty1.gif
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 9.8 KiB

After

Width:  |  Height:  |  Size: 10 KiB

BIN
html/images/tty2.gif
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 10 KiB

After

Width:  |  Height:  |  Size: 10 KiB

BIN
html/images/tty3.gif
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 9.0 KiB

After

Width:  |  Height:  |  Size: 9.9 KiB

35
html/programs/mbtask.html
View File

@ -11,7 +11,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 12-Nov-2001</h5>
<h5>Last update 29-Dec-2001</h5>
<P>&nbsp;<P>
<H1>mbtask - MBSE BBS Taskmanager</H1>
@ -28,18 +28,18 @@
This deamon keeps track of all client actions,
does the logging for the clients, does database locking, authorizes clients,
set/resets users "do not disturb flags", sends and receives chat messages,
keeps track of Zone Mail Hour and the BBS open/close status. Communication
between <strong>mbsed</strong> and the client programs is done via Unix
keeps track of Zone Mail Hour, the status of the mail and files in the outbound,
and the BBS open/close status.
Communication between <strong>mbsed</strong> and the client programs is done via Unix
Datagram sockets. The protocol used to communicate between <strong>mbtask</strong>
and the clients is explained later.
This daemon also watches the semafore directory for some special files.
It also starts programs when they are needed.
The very first time <b>mbtask</b> is started it creates a default config.data and task.data,
the main configuration and task configuration files
the main configuration and task configuration files.
Then it calls <b>mbsetup init</b> to build the default databases.
<b>mbtask</b> should be started at system boot so the bbs system will start working.
The init script that is installed on your system will do that.
This program is introduced with MBSE BBS v0.33.16
and replaces the run_inout and mailer scripts that were called by cron every minute.
<P>
After startup and initalization <b>mbtask</b> runs internally once per second forever.
If there is nothing to do then this time will slowly increase upto 5 seconds. This time will be reset
@ -60,12 +60,19 @@ But before any program is started a number of things are checked:
will shutdown and power off, that's why it's fatal and there is no way back.<br>
<LI>The status of the bbs will be checked, is it open or closed. If it is closed, no
jobs will be started.
<LI>The Zone Mail Hour is checked. If ZMH begins the semafore's <b>zmh</b> is created and
a outbound scan is forced.
If ZMH ends the semafore <b>zmh</b> is removed a new outbound scan is forced.
<LI>The Zone Mail Hour is checked. If ZMH begins the semafore's <b>zmh</b> is
created.
If ZMH ends the semafore <b>zmh</b> is removed.
<LI>Each twenty seconds a ping is send to the IP addresses defined with <b>mbsetup</b> to
check if the internet can be reached. If both ping addresses fail, it is assumed that
the internet can't be reached. <i>Note: this is for future use!</i>
the internet can't be reached. After a status change, the outbound will be
scanned.
<LI>Scan the mailer outbound for work. This builds a list of nodes with mail
in the outbound and sets the necessary flags on nodes who may be called.
It will also set a time when something will change for a node, ie. a zone
mail hour is reached, or a mail window for a node with Txx flags is
reached. Internally this scheduler runs at the UTC clock because Fidonet
has all times defined in UTC.
</OL>
Each new minute the timestamp of semafore <b>mbtask.last</b> is updated so that you can check that
<b>mbtask</b> is running. Also each minute is checked if the system configuration files are
@ -119,7 +126,7 @@ of the bbs structure.
<H3>Security.</H3>
<P>
<strong>mbtask</strong is installed setuid root. This is needed to initialize
<strong>mbtask</strong> is installed setuid root. This is needed to initialize
a raw socket for the ping function. After that is done the privilege drops to
user <strong>mbse</strong> before the child process is created and the rest
of the initialisation is done.
@ -240,7 +247,7 @@ Reply: 100:1,n; n: 0=Ok, 1=Do not disturb, 2=Buffer full
-CKCH:2,channel,user; Kill user chatmode (for Sysops and moderators).
Group G, Global commands.
Group G, Global commands.
Command: GNOP:0; No OPerations.
Reply: 100:0; Ok.
@ -313,8 +320,8 @@ are retrieved from /etc/mtab which is the actual mountstatus. This is used
by the <b>mbmon</b> program to get a "live" view of your filesystems.
<P>&nbsp;<P>
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0" width="33" height="35"> Back to Main index</A>
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0">Back to index</A>&nbsp;
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0">Back to Main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

139
html/setup/taskmgr.html
View File

@ -1,67 +1,72 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Task Manager.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 07-Jul-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Task Manager.</H1>
<P>
<H3>Introduction</H3>
<P>
The task manager is the daemon which controls the MBSE BBS. It watches semafore's and spawns
programs in the background. The behaviour is setup in this screen.
<P>
<H3>Edit Task Manager</H3>
<P>
<pre>
<b>Mailout </b>Action for semafore mailout.
<b>Mailin </b>Action for semafore mailin.
<b>Newnews </b>Action for semafore newnews.
<b>Index 1 </b>Nodelist compiler 1 for semafore mbindex.
<b>Index 2 </b>Nodelist compiler 2 for semafore mbindex.
<b>Index 3 </b>Nodelist compiler 3 for semafore mbindex.
<b>Msglink </b>Action for semafore msglink.
<b>Reqindex </b>Action for semafore reqindex.
<b>ISP conn </b>Not in use yet!
<b>ISP disc </b>Not in use yet!
<b>Ping #1 </b>IP address of node to ping to check the internet.
<b>Ping #2 </b>IP address of second node to ping to check the internet.
<b>ISP blks </b>Set to true if you have internet dialup and if it blocks normal dial.
<b>Max Load </b>Max system load until processing is suspended.
<b>ZMH start </b>Start of Zone Mail Hour in UTC time.
<b>ZMH end </b>End of Zone Mail Hour in UTC time.
<b>Debug </b>Enable debug logging.
<b>Max POTS </b>Maximum simultaneous outgoing calls (for now ISDN + POTS + TCP/IP).
<b>Max ISDN </b>Not in use yet!
<b>Max TCP </b>Not in use yet!
</pre>
<P>
Default are the original MBSE commands filled in, but you could also call
shell scripts. As you can see, the task manager is not yet finished.
<P>
The two IP addresses to ping need to be IP addresses, not hostnames. This is the
most reliable way to check the connection. You should enter the IP addresses of
the nameservers of your own ISP here. One of these will always be up, so if one
of these can be reached, the internet connection is assumed to be alive.
<P>
<IMG SRC="../images/taskmgr.gif" Border="0">
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Task Manager.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Dec-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Task Manager.</H1>
<P>
<H3>Introduction</H3>
<P>
The task manager is the daemon which controls the MBSE BBS. It watches semafore's and spawns
programs in the background. It also watches the outbound to see if there are
nodes to call.
The behaviour is setup in this screen.
<P>
<H3>Edit Task Manager</H3>
<P>
<pre>
<b>Mailout </b>Action for semafore mailout.
<b>Mailin </b>Action for semafore mailin.
<b>Newnews </b>Action for semafore newnews.
<b>Index 1 </b>Nodelist compiler 1 for semafore mbindex.
<b>Index 2 </b>Nodelist compiler 2 for semafore mbindex.
<b>Index 3 </b>Nodelist compiler 3 for semafore mbindex.
<b>Msglink </b>Action for semafore msglink.
<b>Reqindex </b>Action for semafore reqindex.
<b>ISP conn </b>Not in use yet!
<b>ISP disc </b>Not in use yet!
<b>Ping #1 </b>IP address of node to ping to check the internet.
<b>Ping #2 </b>IP address of second node to ping to check the internet.
<b>ISP blks </b>Set to true if you have internet dialup and it blocks normal dial.
<b>Max Load </b>Max system load until processing is suspended.
<b>ZMH start </b>Start of Zone Mail Hour in UTC time.
<b>ZMH end </b>End of Zone Mail Hour in UTC time.
<b>Debug </b>Enable debug logging.
<b>Max POTS </b>Maximum simultaneous outgoing calls over analogue modems.
<b>Max ISDN </b>Maximum simultaneous outgoing calls over ISDN channels.
<b>Max TCP </b>Maximum simultaneous outgoing calls over the internet.
</pre>
<P>
Default are the original MBSE commands filled in, but you could also call
shell scripts.
<P>
The two IP addresses to ping need to be IP addresses, not hostnames. This is the
most reliable way to check the connection. You should enter the IP addresses of
the nameservers of your own ISP here. One of these will always be up, so if one
of these can be reached, the internet connection is assumed to be alive. The
status of the internet connection is used to decide if it is allowed (and
possible) to call TCP/IP nodes. Calling these nodes is not depending on ZMH
unless the destination is not a CM node.
<P>
<IMG SRC="../images/taskmgr.gif" Border="0">
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

146
html/setup/ttyinfo.html
View File

@ -1,73 +1,73 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - TTY Lines.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - TTY Lines.</H1>
<P>
<h3>Introduction.</H3>
<P>
For each line your bbs has you must setup a tty line. This also includes
console lines (for local login), network lines for internet and lan connections
and X-terminal connections, ISDN lines, and Analogue modem lines. If a call
comes in over a tty you didn't define, that call is refused. So if you are
directly connected to the internet, and have only 5 network tty's defined,
then maximum 5 users are allowed to telnet to your bbs via the internet.
<p>
One thing about the portspeed, this is only needed for devices connected to
serial ports such as modems and external ISDN adapters. For network tty's and
internal ISDN cards this should be set to zero. If you set it to some other value,
things still word but you will get error messages in the logs.
<p>
A note about the EMSI flags, this <u>must</u> match your modem capabilities, if
not dialout will not work correct. It is used to see which line to use to call
a certain node. If you add the X75 flag on an analogue line, your system will try to
call ISDN nodes using an analogue modem. So these are not your nodelist flags as they
may represent combined ISDN and analogue flags but the flags that belong to a modem.
<p>&nbsp;<p>
<H3>Setup a line.</H3>
<p>
<pre>
<strong>Comment </strong>A description for this line.
<strong>TTY device </strong>The tty device name without /dev/
<strong>Phone nr. </strong>The phone number on this line.
<strong>Line Speed </strong>The maximum line speed for this line.
<strong>Fido Flags </strong>The EMSI flags for this line, include your modem flags here!
<strong>Line Type </strong>Can be POTS, ISDN, Network and Local.
<strong>Available </strong>Is this line available for use.
<strong>Auth. log </strong>Not in use yet.
<strong>Honor ZMH </strong>Deny users during ZMH on this line.
<strong>Deleted </strong>If this line must be deleted.
<strong>Callout </strong>Allow calling other systems from this line.
<strong>Portspeed </strong>The "locked" modemspeed, 0 to 4000000 baud, only for serial ports.
<strong>Modemtype </strong>The modem connected to this line.
<strong>EMSI name </strong>The EMSI name presented for this (modem) line.
</pre>
<p>&nbsp;<p>
<H3>Some examples.</H3>
<P>
<IMG SRC="../images/tty.gif" width="589" height="343"><P>
<IMG SRC="../images/tty1.gif" width="576" height="344"><P>
<IMG SRC="../images/tty2.gif" width="589" height="342"><P>
<IMG SRC="../images/tty3.gif" width="589" height="343"><P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - TTY Lines.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Dec-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - TTY Lines.</H1>
<P>
<h3>Introduction.</H3>
<P>
For each line your bbs has you must setup a tty line. This also includes
console lines (for local login), network lines for internet and lan connections
and X-terminal connections, ISDN lines, and Analogue modem lines. If a call
comes in over a tty you didn't define, that call is refused. So if you are
directly connected to the internet, and have only 5 network tty's defined,
then maximum 5 users are allowed to telnet to your bbs via the internet.
<p>
One thing about the portspeed, this is only needed for devices connected to
serial ports such as modems and external ISDN adapters. For network tty's and
internal ISDN cards this should be set to zero. If you set it to some other value,
things still word but you will get error messages in the logs.
<p>
A note about the EMSI flags, this <u>must</u> match your modem capabilities, if
not dialout will not work correct. It is used to see which line to use to call
a certain node. If you add the X75 flag on an analogue line, your system will try to
call ISDN nodes using an analogue modem. So these are not your nodelist flags as they
may represent combined ISDN and analogue flags but the flags that belong to a modem.
<p>&nbsp;<p>
<H3>Setup a line.</H3>
<p>
<pre>
<strong>Comment </strong>A description for this line.
<strong>TTY device </strong>The tty device name without /dev/
<strong>Phone nr. </strong>The phone number on this line.
<strong>Line Speed </strong>The maximum line speed for this line.
<strong>Fido Flags </strong>The EMSI flags for this line, include your modem flags here!
<strong>Line Type </strong>Can be POTS, ISDN, Network and Local.
<strong>Available </strong>Is this line available for use.
<strong>Auth. log </strong>Not in use yet.
<strong>Honor ZMH </strong>Deny users during ZMH on this line.
<strong>Deleted </strong>If this line must be deleted.
<strong>Callout </strong>Allow calling other systems from this line.
<strong>Portspeed </strong>The "locked" modemspeed, 0 to 4000000 baud, only for serial ports.
<strong>Modemtype </strong>The modem connected to this line.
<strong>EMSI name </strong>The EMSI name presented for this (modem) line.
</pre>
<p>&nbsp;<p>
<H3>Some examples.</H3>
<P>
<IMG SRC="../images/tty.gif" ALT="Overview of tty ports"><P>
<IMG SRC="../images/tty1.gif" ALT="A analogue modem port at COM1"><P>
<IMG SRC="../images/tty2.gif" ALT="A ISDN channel"><P>
<IMG SRC="../images/tty3.gif" ALT="A network (internet telnet) port"><P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>