Updated nodes setup documentation
This commit is contained in:
Michiel Broek
parent
31eb206a33
commit
7fc02bdac2
@ -29,7 +29,8 @@ H_IMAGES = images/b_arrow.gif images/magic.gif images/nodes1.png \
|
||||
images/domains.gif images/mbsetup1.6.S.gif images/nodes3.png \
|
||||
images/e_menu.png images/mbsetup1.6.gif images/nodes4.gif \
|
||||
images/emareas.gif images/mbsetup2.gif images/nodes5.gif \
|
||||
images/nodes6.gif images/nodes7.png images/nodes8.gif \
|
||||
images/nodes6.gif images/nodes7.png images/nodes8.png \
|
||||
images/nodes9.png \
|
||||
images/emgroup.gif images/modems0.gif images/oneliner.gif \
|
||||
images/fdb.gif images/newfiles.gif images/protocol.gif \
|
||||
images/fegroup.gif images/newgroups.gif images/rarrow.gif \
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 9.4 KiB After Width: | Height: | Size: 9.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 12 KiB |
BIN
html/images/nodes8.png
Normal file
BIN
html/images/nodes8.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
BIN
html/images/nodes9.png
Normal file
BIN
html/images/nodes9.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 6.7 KiB |
@ -12,7 +12,7 @@
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<BLOCKQUOTE>
|
||||
<div align=right><h5>Last update 13-Jul-2002</h5></div>
|
||||
<div align=right><h5>Last update 10-Aug-2002</h5></div>
|
||||
|
||||
<div align=center><H1>MBSE BBS Setup - Fidonet nodes.</H1></div>
|
||||
<P>
|
||||
@ -22,11 +22,11 @@
|
||||
Unlike many other bbs packages, for each node you need only one record. If you
|
||||
have a relation with a node for one network with costsharing, and other
|
||||
networks without costsharing you need two records for that node. For each node
|
||||
you can setup the aka's, mail, files and session handshake. There are eight
|
||||
you can setup the aka's, mail, files and session handshake. There are nine
|
||||
screens for each node.
|
||||
<p> <p>
|
||||
|
||||
<H3>Edit general setup</H3>
|
||||
<H3>1. Edit general setup</H3>
|
||||
<p>
|
||||
This screen has the general information for the node. The contact info fields are
|
||||
just for private use, these fields are only used in this screen. The Outbox dir is for
|
||||
@ -74,47 +74,75 @@ deleted.</td></tr>
|
||||
<IMG SRC="../images/nodes1.png">
|
||||
<P> <p>
|
||||
|
||||
<H3>Edit nodes aka's</H3>
|
||||
<H3>2. Edit nodes aka's</H3>
|
||||
<p>
|
||||
In this screen you can setup 20 aka's for the node.
|
||||
<p>
|
||||
<IMG SRC="../images/nodes2.png">
|
||||
<P> <p>
|
||||
|
||||
<H3>Edit node session</H3>
|
||||
<H3>3. Edit node session</H3>
|
||||
<p>
|
||||
In this screen you can setup the session defaults. Items 7 and 8 will be added later.
|
||||
<p><table>
|
||||
<tr><th nowrap align=left valign=top>Session passwd</th><td>This is the mailer session password.
|
||||
<tr><th nowrap align=left valign=top>Dial command</th><td>You can put an override here for the normal dial command. If you leave this empty the command from the modem setup is used.
|
||||
<tr><th nowrap align=left valign=top>Phone number 1</th><td>An alternative phone number/ip address to dial.
|
||||
<tr><th nowrap align=left valign=top>Phone number 2</th><td>An alternative phone number/ip address to dial. Use these above commands if the node has another phone number as mentioned in the nodelist.
|
||||
<tr><th nowrap align=left valign=top>Session passwd</th><td>This is the mailer
|
||||
session password.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Dial command</th><td>You can put an
|
||||
override here for the normal dial command. If you leave this empty the command
|
||||
from the modem setup is used.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Phone number 1</th><td>An alternative phone
|
||||
number/ip address to dial.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Phone number 2</th><td>An alternative phone
|
||||
number/ip address to dial. Use these above commands if the node has another
|
||||
phone number as mentioned in the nodelist.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Nodelist flags</th><td>Override for the
|
||||
nodelist flags, the nodelist flags are completly ignored if you enter something
|
||||
here so make sure all flags you need are here. All aka's of this node will use
|
||||
the same flags. This can be usefull to force calling this node via the internet.
|
||||
the same flags. This can be usefull to force calling this node via the
|
||||
internet.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Inet hostname</th><td>The FQDN hostname or
|
||||
IP address of this node. This replaces the original system name from the
|
||||
nodelist and this is then used to make the internet TCP/IP connection. This can
|
||||
be usefull if the FQDN is not present in the nodelist.
|
||||
<tr><th nowrap align=left valign=top>No EMSI</th><td>Disable EMSI handshake.
|
||||
<tr><th nowrap align=left valign=top>No YooHoo/2U2</th><td>Disable FTSC-0006 handshake.
|
||||
<tr><th nowrap align=left valign=top>No Filerequest</th><td>Disable filerequest from this node.
|
||||
<tr><th nowrap align=left valign=top>Don't call</th><td>Do not call this node.
|
||||
<tr><th nowrap align=left valign=top>8.3 names</th><td>Set this if the node only accepts 8.3 filenames.
|
||||
<tr><th nowrap align=left valign=top>No Zmodem</th><td>Disable Zmodem protocol.
|
||||
<tr><th nowrap align=left valign=top>No Zedzap</th><td>Disable Zedzap protocol.
|
||||
<tr><th nowrap align=left valign=top>No Hydra</th><td>Disable Hydra protocol.
|
||||
<tr><th nowrap align=left valign=top>No TCP/IP IBN</th><td>Disbale TCP/IP IBN (binkp) protocol.
|
||||
<tr><th nowrap align=left valign=top>No TCP/IP IFC</th><td>Disable TCP/IP IFC (ifcico) protocol.
|
||||
<tr><th nowrap align=left valign=top>No TCP/IP ITN</th><td>Disable TCP/IP ITN (telnet) protocol.
|
||||
be usefull if the FQDN is not present in the nodelist.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Outbound sess.</th><td>Outbound session
|
||||
method, choices are <b>Direct</b> and <b>Directory</b>. Direct means normal
|
||||
classic mailer connections. Directory means that everything is put in a
|
||||
directory from which the other node can fetch the mail and files using ftp
|
||||
protocol.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Inbound sess.</th><td>Inbound session
|
||||
method, choices are <b>Direct</b> and <b>Directory</b>. Direct means normal
|
||||
classic mailer connections. Directory means that inbound mail and files are
|
||||
expected in a directory were it is stored by the node using ftp
|
||||
protocol.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>No EMSI</th><td>Disable EMSI
|
||||
handshake.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>No YooHoo/2U2</th><td>Disable FTSC-0006
|
||||
handshake.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>No Filerequest</th><td>Disable filerequest
|
||||
from this node.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Don't call</th><td>Do not call this
|
||||
node.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>8.3 names</th><td>Set this if the node only
|
||||
accepts 8.3 filenames.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>No Zmodem</th><td>Disable Zmodem
|
||||
protocol.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>No Zedzap</th><td>Disable Zedzap
|
||||
protocol.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>No Hydra</th><td>Disable Hydra
|
||||
protocol.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>No TCP/IP IBN</th><td>Disbale TCP/IP IBN
|
||||
(binkp) protocol.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>No TCP/IP IFC</th><td>Disable TCP/IP IFC
|
||||
(ifcico) protocol.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>No TCP/IP ITN</th><td>Disable TCP/IP ITN
|
||||
(telnet) protocol.</td></tr>
|
||||
</table>
|
||||
<p>
|
||||
<IMG SRC="../images/nodes3.png">
|
||||
<P> <p>
|
||||
|
||||
|
||||
<H3>Edit node - mail processing</H3>
|
||||
<H3>4. Edit node - mail processing</H3>
|
||||
<P>
|
||||
<p><table>
|
||||
<tr><th nowrap align=left valign=top>PKT password</th><td>The password to insert in .pkt files.
|
||||
@ -129,7 +157,7 @@ be usefull if the FQDN is not present in the nodelist.
|
||||
<IMG SRC="../images/nodes4.gif">
|
||||
<P> <p>
|
||||
|
||||
<H3>Edit mail groups</H3>
|
||||
<H3>5. Edit mail groups</H3>
|
||||
<P>
|
||||
Here you can tag which mail groups are available for this node. Note that all
|
||||
groups are visible here, even for networks this node has no aka's in. Be
|
||||
@ -138,7 +166,7 @@ carefull not to allow a node to connect areas from networks he has no aka in.
|
||||
<IMG SRC="../images/nodes5.gif">
|
||||
<P> <p>
|
||||
|
||||
<H3>File setup</H3>
|
||||
<H3>6. File setup</H3>
|
||||
<P>
|
||||
<p><table>
|
||||
<tr><th nowrap align=left valign=top>Files password</th><td>The password for .tic files.
|
||||
@ -162,14 +190,164 @@ carefull not to allow a node to connect areas from networks he has no aka in.
|
||||
<IMG SRC="../images/nodes6.gif">
|
||||
<P> <p>
|
||||
|
||||
<H3>File groups</H3>
|
||||
<H3>7. File groups</H3>
|
||||
<P>
|
||||
The same story as for mail groups is true for the file groups.
|
||||
<P>
|
||||
<IMG SRC="../images/nodes7.png">
|
||||
<P> <p>
|
||||
|
||||
<H3>Statistics</H3>
|
||||
<H3>8. Directory session</H3>
|
||||
<P>
|
||||
Setup in this screen is needed if you selected Inbound and or Outbound session
|
||||
as Directory session. The node is then getting and bringing mail using the ftp
|
||||
protocol and no normal mailer connects are being used anymore.
|
||||
This may be a good solution for points, they only need a simple mailreader and a
|
||||
tosser. The mail is transferred by the <b>mbfido</b> program, during the toss or
|
||||
tic command after the normal inbound is processed <b>mbfido</b> will look for nodes inbound
|
||||
directories to process. When mail is added to the outbound, mail for nodes with
|
||||
directory sessions is not stored in the normal Binley Style Outbound but in the
|
||||
session outbound directory.<br>
|
||||
You need to setup a ftp account for this node and the best thing is to
|
||||
set this up so that the other node is forced in a chroot environment, ie. make
|
||||
it so that the node only sees his own directories and cannot leave that. The ftp
|
||||
account needs to be a member of group bbs because mbfido needs access to the
|
||||
files as well as the node. The nodes account needs also to be a member of group
|
||||
bbsftp for the chroot environment.
|
||||
The node needs umask 002 so that files that he puts
|
||||
there will have group read/write access. During toss mbfido also stores the
|
||||
files with group read/write access so that the node can remove the files when he
|
||||
has fetched all files. Directory locking is supported and is compatible with
|
||||
other mailers that support ftp. Here is a small sample of protftp.conf for use
|
||||
with directory sessions:
|
||||
<pre>
|
||||
# This is /etc/proftpd.conf for use with mbsebbs ftp mail
|
||||
# sessions and anonymous ftp access.
|
||||
# It assumes that you have a user/group "nobody" and "ftp"
|
||||
# for normal/anonymous operation.
|
||||
# It also assumes you have a group bbsftp were ftp mail users
|
||||
# must be a member of.
|
||||
#
|
||||
ServerName "Seaport ProFTPD server"
|
||||
ServerType inetd
|
||||
DefaultServer on
|
||||
#
|
||||
# Port 21 is the standard FTP port.
|
||||
Port 21
|
||||
# Umask 002 is to force new dirs and files to be group writable.
|
||||
Umask 002
|
||||
#
|
||||
# To prevent DoS attacks, set the maximum number of child processes
|
||||
# to 30.
|
||||
MaxInstances 30
|
||||
#
|
||||
# Set the user and group that the server normally runs at.
|
||||
User nobody
|
||||
Group nogroup
|
||||
#
|
||||
SystemLog /var/log/proftpd
|
||||
TransferLog /var/log/xferlog
|
||||
#
|
||||
# Anonymous ftp and members of group bbsftp have a chroot environment.
|
||||
DefaultRoot ~ bbsftp
|
||||
#
|
||||
# Normally, we want files to be overwriteable.
|
||||
<Directory /*>
|
||||
AllowOverwrite on
|
||||
</Directory>
|
||||
#
|
||||
# A basic anonymous FTP server configuration.
|
||||
# To enable this, remove the user ftp from /etc/ftpusers.
|
||||
<Anonymous ~ftp>
|
||||
RequireValidShell off
|
||||
User ftp
|
||||
Group ftp
|
||||
# We want clients to be able to login with "anonymous" as well as "ftp"
|
||||
UserAlias anonymous ftp
|
||||
#
|
||||
# Limit the maximum number of anonymous logins
|
||||
MaxClients 50
|
||||
#
|
||||
# We want 'welcome.msg' displayed at login, and '.message' displayed
|
||||
# in each newly chdired directory.
|
||||
DisplayLogin welcome.msg
|
||||
DisplayFirstChDir .welcome
|
||||
DisplayReadme README
|
||||
#
|
||||
# Display .dotfiles and .dirs
|
||||
LsDefaultOptions "-a"
|
||||
#
|
||||
# Limit WRITE everywhere in the anonymous chroot
|
||||
<Limit WRITE>
|
||||
DenyAll
|
||||
</Limit>
|
||||
#
|
||||
# An upload directory that allows storing files but not retrieving
|
||||
# or creating directories.
|
||||
<Directory incoming/*>
|
||||
<Limit READ>
|
||||
DenyAll
|
||||
</Limit>
|
||||
|
||||
<Limit STOR>
|
||||
AllowAll
|
||||
</Limit>
|
||||
</Directory>
|
||||
#
|
||||
</Anonymous>
|
||||
</pre>
|
||||
Here are some examples to create an account, first create the extra group
|
||||
bbsftp:
|
||||
<pre>
|
||||
groupadd bbsftp
|
||||
</pre>
|
||||
Then create accounts like this:
|
||||
<pre>
|
||||
useradd -g bbs -G bbsftp -d /opt/mbse/var/bbsftp/irex -s /bin/bash -c "FTP Mail account" irex
|
||||
</pre>
|
||||
Then give the node a password for the ftp login. Note that this account has a
|
||||
shell, proftpd needs a valid shell to allow access. If the node tries to telnet
|
||||
to your bbs he can't login with this account if you use <b>mblogin</b>, this is
|
||||
because the node is not in the bbs userfile. If you system allows it, the node
|
||||
can access the shell using rlogin or ssh.<br>
|
||||
Now the items to setup for the directory sessions:
|
||||
<p><table>
|
||||
<tr><th nowrap align=left valign=top colspan=2>Outbound settings</th></tr>
|
||||
<tr><th nowrap align=left valign=top>Files path</th><td>The path were to store
|
||||
the outbound mail and files.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Check for lock</th><td>If we need to check
|
||||
for a lockfile before adding files.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Wait clear lock</th><td>Wait for the lock
|
||||
to clear if present or not. If set to yes and there is a lock created by the
|
||||
node then mbfido will wait for maximum 10 minutes for the lock to disappear. If
|
||||
set to no, mbfido skips this node and will add mail and files at a later time.
|
||||
<tr><th nowrap align=left valign=top>Check lockfile</th><td>The full filename
|
||||
and path of the lockfile to check for.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Create lock</th><td>If mbfido should create
|
||||
a lock during the time it will add mail and files.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Create lockfile</th><td>The full filename
|
||||
and path of the lockfile to create.</td></tr>
|
||||
<tr><th nowrap align=left valign=top colspan=2>Inbound settings</th></tr>
|
||||
<tr><th nowrap align=left valign=top>Files path</th><td>The path from were to
|
||||
get the inbound mail and files.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Check for lock</th><td>If we need to check
|
||||
for a lockfile before getting files.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Wait clear lock</th><td>Wait for the lock
|
||||
to clear if present or not. If set to yes and there is a lock created by the
|
||||
node then mbfido will wait for maximum 10 minutes for the lock to disappear. If
|
||||
set to no, mbfido skips this node and will scan this directory at a later time.
|
||||
<tr><th nowrap align=left valign=top>Check lockfile</th><td>The full filename
|
||||
and path of the lockfile to check for.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Create lock</th><td>If mbfido should create
|
||||
a lock during the time it will get mail and files.</td></tr>
|
||||
<tr><th nowrap align=left valign=top>Create lockfile</th><td>The full filename
|
||||
and path of the lockfile to create.</td></tr>
|
||||
</table>
|
||||
<P>
|
||||
<IMG SRC="../images/nodes8.png">
|
||||
<P> <P>
|
||||
|
||||
<H3>9. Statistics</H3>
|
||||
<P>
|
||||
In this statistics screen you can see the mail and files flow with this
|
||||
node. Values are stored for the current week, the previous week, the
|
||||
@ -177,7 +355,7 @@ current month and previous month and the overall total since you defined
|
||||
this node. There are actual 12 months of statistics stored in the nodes
|
||||
record, only 2 are visible.
|
||||
<P>
|
||||
<IMG SRC="../images/nodes8.gif">
|
||||
<IMG SRC="../images/nodes9.png">
|
||||
<P>
|
||||
|
||||
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0">Back to index</A>
|
||||
|
||||
Reference in New Issue
Block a user