Updated documentaion for ISDN modems
This commit is contained in:
parent
8094a0d1d7
commit
7698ede7ab
@ -11,7 +11,7 @@
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<BLOCKQUOTE>
|
||||
<h5>Last update 29-Jan-2001</h5>
|
||||
<h5>Last update 09-Dec-2001</h5>
|
||||
<P> <P>
|
||||
|
||||
<H1 ALIGN="CENTER">Setup mgetty for MBSE BBS</H1>
|
||||
@ -19,20 +19,26 @@
|
||||
To handle incoming calls you can use <strong>mgetty</strong> written by
|
||||
Gert Doering, (gert@greenie.muc.de). Others may work. You have to compile
|
||||
<strong>mgetty</strong> with the -DFIDO flag to accept Fidonet mailer calls.
|
||||
If you want incoming PPP calls as well, add the -DAUTO_PPP as well. Below
|
||||
you can see the mgetty.config and login.config for mgetty that I use. I
|
||||
have also included a part of my /etc/inittab to show how <strong>mgetty
|
||||
If you want incoming PPP calls as well, add the -DAUTO_PPP as well. If you want
|
||||
to use ISDN, make sure you have ISDN support compiled in the kernel.
|
||||
Below you can see the mgetty.config and login.config for mgetty that you may
|
||||
need.
|
||||
I have also included a part of my /etc/inittab to show how <strong>mgetty
|
||||
</strong> will spawn from <strong>init</strong>.
|
||||
<P>
|
||||
|
||||
<HR>
|
||||
<PRE>
|
||||
# inittab This is only a part of my /etc/inittab!
|
||||
# inittab This is only a part of /etc/inittab!
|
||||
# In this example it runs in runlevel 3 and 4.
|
||||
#
|
||||
# Serial lines
|
||||
s1:34:respawn:/usr/local/sbin/mgetty -i /opt/mbse/etc/issue ttyS0
|
||||
#
|
||||
# ISDN lines, two channels
|
||||
I1:34:respawn:/usr/local/sbin/mgetty -i /opt/mbse/etc/issue ttyI0
|
||||
I2:23:respawn:/usr/local/sbin/mgetty -i /opt/mbse/etc/issue ttyI1
|
||||
#
|
||||
# End of /etc/inittab
|
||||
</PRE>
|
||||
<HR>
|
||||
@ -77,6 +83,21 @@ switchbd 19200
|
||||
modem-type cls2
|
||||
init-chat "" \d\dAT&F&C1&D3X4W2B0M0Q0V1H0&K3S0=0 OK
|
||||
#
|
||||
#
|
||||
# ISDN ports.
|
||||
# With AT&E you set the MSN/EAZ the device should listen to.
|
||||
# This should for an MSN be your telephone number _with_ the area
|
||||
# code but _without_ the leading 0.
|
||||
# For an EAZ the last digit of your EAZ.
|
||||
#
|
||||
port ttyI0
|
||||
modem-type data
|
||||
init-chat "" ATZ OK AT&E714015437&W0 OK AT&B512 OK
|
||||
#
|
||||
port ttyI1
|
||||
modem-type data
|
||||
init-chat "" ATZ OK AT&E714017198&W0 OK AT&B512 OK
|
||||
#
|
||||
# end of mgetty.config
|
||||
</PRE>
|
||||
<HR>
|
||||
@ -117,18 +138,13 @@ init-chat "" \d\dAT&F&C1&D3X4W2B0M0Q0V1H0&K3S0=0 OK
|
||||
#
|
||||
* - - /bin/login @
|
||||
#
|
||||
# You might use this instead, it will directly start the BBS when the call
|
||||
# is not a PPP call and not a Fidonet mailer. Use only one of these two!
|
||||
# THIS IS NOT YET TESTED!
|
||||
#
|
||||
* - - /opt/mbse/bin/mbsebbs
|
||||
#
|
||||
# end of login.config
|
||||
</PRE>
|
||||
<HR>
|
||||
|
||||
<P>
|
||||
If you use /bin/login the users can get confused by the Unix login prompt.
|
||||
Because we use /bin/login the users can get confused by the Unix login prompt.
|
||||
Most of them are used to DOS based bbs systems and will try to login with
|
||||
two names which won't work of course. For this reason I have added the
|
||||
<strong>-i /opt/mbse/etc/issue</strong> options to the <strong>mgetty</strong>
|
||||
@ -145,8 +161,10 @@ explaining users how to login to start the bbs. It could look like this:<br>
|
||||
\___)=(___/
|
||||
Powered by Linux.
|
||||
|
||||
To start the bbs login with "bbs" without quotes.
|
||||
Voor het bbs login met "bbs" zonder aanhalingstekens.
|
||||
To register as a new user login with the name "bbs" without quotes.
|
||||
Existing users must login with their unix name (one word).
|
||||
Nieuwe gebruikers kunnen inloggen met "bbs" zonder aanhalingstekens.
|
||||
Bestaande gebruikers moeten inloggen met hun unix naam (een woord).
|
||||
</pre>
|
||||
There is a default /opt/mbse/etc/issue installed by the installation script.
|
||||
You need to edit this to insert your bbs name in it or even completely replace
|
||||
@ -162,10 +180,12 @@ chmod 666 /dev/ttyS0
|
||||
chown uucp.uucp /dev/ttyS0
|
||||
exit
|
||||
</pre>
|
||||
Note that /dev/ttyS0 is for COM1, /dev/ttyS1 for COM2 etc.
|
||||
Note that /dev/ttyS0 is for COM1, /dev/ttyS1 for COM2 etc. This is not a nice
|
||||
solution. If youre system allows it, try to add the the user <b>mbse</b> as
|
||||
a legal user of your serial ports. Most distributions have some tool for this.
|
||||
<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>
|
||||
</BLOCKQUOTE>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
Reference in New Issue
Block a user