Made routing tables and added docs

This commit is contained in:
Michiel Broek 2002-07-25 20:08:46 +00:00
parent ac709b7eda
commit 9ad2e16006
9 changed files with 86 additions and 15 deletions

View File

@ -1,10 +1,5 @@
$Id$
WARNING WARNING WARNING WARNING
DO NOT USE ON PRODUCTION SYSTEMS, ONLY FOR TESTING
MBSEBBS History.
@ -30,9 +25,9 @@ v0.35.03 06-Jul-2002
When a new tic area was created the first file received for
that area was refused.
Fixed a few problems with local UUCP created netmails.
* Added very experimental routing table.
* Test for local node moved in sequence, testing is now done
so as real routing will be done.
Added routing tables for special cases. Most systems don't
need this.
The route test command now works exactly as netmails do.
newuser:
Check for Unix accounts is now case sensitive.
@ -59,7 +54,7 @@ v0.35.03 06-Jul-2002
When a JAM messagebase path is changed in one of the message
area, filefind and newfiles records are automatic updated if
they were connected to that area.
Added setup for routing table.
Added setup for routing the table.
script:
The bbsdoor.sh and rundoor.sh scripts are now only installed

6
TODO
View File

@ -60,8 +60,6 @@ mbfido:
N: Process To: and Cc: lines in messages gated from Fido to Internet.
U: Add routing table to override standard routing. UNDER TEST NOW!
N: Add traffic to html.nodes
N: Add stats for posts made by external programs.
@ -70,6 +68,8 @@ mbfido:
L: A separate log for processed area/filemgr requests.
N: Add logging info about added/removed areas.
mbcico:
L: Implement modem connect response translation for ISDN lines, i.e.
make the CAUSE responses human readable. see McMail for this
@ -118,6 +118,8 @@ mbsetup:
N: Add switch for file area to skip checking and indexing.
N: Add logging info about added/removed areas.
L: Generate crossreference document:
File Areas <=> BBS groups
File Areas <=> Newfiles groups

View File

@ -43,7 +43,8 @@ H_IMAGES = images/b_arrow.gif images/magic.gif images/nodes1.png \
images/mbse.jpg images/taskmgr.png images/mbsebbs.gif \
images/mbsebbs.png images/users2.png images/hand.up.gif \
images/dream1.png images/dream2.png images/dream3.png \
images/tdream1.gif images/tdream2.gif images/tdream3.gif
images/tdream1.gif images/tdream2.gif images/tdream3.gif \
images/route1.png images/route2.png
H_LICENSE = license/copying.html license/hydracom.html license/index.htm \
license/jam.html
@ -82,7 +83,7 @@ H_SETUP = setup/archiver.html setup/index.htm setup/bbs.html \
setup/newgroups.html setup/files.html setup/nodes.html \
setup/ttyinfo.html setup/global.html setup/users.html \
setup/hatch.html setup/virscan.html setup/services.html \
setup/domains.html setup/taskmgr.html
setup/domains.html setup/taskmgr.html setup/route.html
FILES = $(H_BASE) $(H_FTSC) $(H_IMAGES) $(H_LICENSE) $(H_MENUS) $(H_MISC) $(H_PROGS) $(H_SETUP) Makefile

Binary file not shown.

Before

Width:  |  Height:  |  Size: 11 KiB

After

Width:  |  Height:  |  Size: 11 KiB

BIN
html/images/route1.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.2 KiB

BIN
html/images/route2.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.8 KiB

View File

@ -16,7 +16,7 @@
<div align=center><h1>MBSE BBS System Guide v0.35.01</h1></div>
<HR>
<div align=right><h5>Last update 05-Jun-2002</h5></div>
<div align=right><h5>Last update 25-Jul-2002</h5></div>
<P>
@ -84,6 +84,7 @@
<li><A HREF="setup/services.html">Edit Services</a>
<li><A HREF="setup/domains.html">Edit Domains</A>
<li><A HREF="setup/taskmgr.html">Edit task manager</A>
<li><A HREF="setup/route.html">Edit Routing Table</a>
<li><A HREF="setup/softinfo.html">Show software information</a>
<li><A HREF="setup/sitedoc.html">Create site documents</a>
</ol>

View File

@ -12,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 27-May-2001</h5>
<h5>Last update 25-Jul-2001</h5>
<P>&nbsp;<P>
<h1>MBSE BBS Setup Guide</h1>
@ -70,6 +70,7 @@ When you start <strong>mbsetup</strong> you will see the following screen:
<li><A HREF="services.html">Edit Services</a>
<li><A HREF="domains.html">Edit Domains</A>
<LI><A HREF="taskmgr.html">Edit Task Manager</A>
<li><A HREF="route.html">Edit Routing Table</A>
<li><A HREF="softinfo.html">Show software information</a>
<li><A HREF="sitedoc.html">Create site documents</a>
</ol>

71
html/setup/route.html Normal file
View File

@ -0,0 +1,71 @@
<HTML>
<!-- $Id$ -->
<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 - Edit Routing Table.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<div align=right><h5>Last update 25-Oct-2001</h5></div>
<div align=center><H1>MBSE BBS Setup - Edit Routing Table.</H1></div>
<P>
<H3>Introduction.</H3>
<P>
First an important note: normal nodes, hubs and hosts should not need this to
setup. MBSE is smart enough to do normal netmail routing using the nodelist.
There are cases when you might need this, for example if you are a RC or if you
have special routing arrangements via internet nodes. Think at least twice
before adding entries here. You can always use the <b>mbfido test</b> command to
check if the standard routing is enough. You should also check to see what you have
done with <b>mbfido test</b> if the entries in this table do what you expect
them to do.
During route tests it is wise to temporary switch on extra debug logging
with mbsetup menu 1.5.16.17 and check the information in the logfile, there is a
lot of information about the descisions that are made.
<P>
When you edit a route table, the entries you add might not be in the right
order, this will be done after you leave the editor. Sorting is done in order of
zone, exact nodes first, then globals. If you end the routing table with a global
route, ie. to All zones, then the standard routing isn't used anymore and only
the table is consulted. This might not be needed, most likely is that you only
need to add the routes to the non-standard nodes. The table is processed from
the first entry to the last and stops when an entry matches. If there was no
match, the default routing will be used.
<P>&nbsp;<P>
<H3>Edit Routing Table.</H3>
<P>
When you open the table you see something like this:<P>
<IMG SRC="../images/route1.png" ALT="Back" Border="0">
<P>
The edit screen looks like this:<P>
<IMG SRC="../images/route2.png" ALT="Back" Border="0">
<pre>
<strong>Mask </strong>The destination mask to test for.
<strong>Action </strong>Route to, Direct or Default.
<strong>Dest addr </strong>The destination node in case of Route to.
<strong>Active </strong>If this rule is active.
<strong>Deleted </strong>If this rule must be deleted.
</pre>
<P>
If the Action is <b>Route to</b> then all mail matching the Mask will be routed
to the node setup in Dest addr. This node must be present in your setup.
If the Mask is <b>Direct</b> then mail to node node(s) matching the Mask will be
sent direct, not routed. If the action is <b>Default</b> then the nodes matching
the Mask will use the standard default routing. More actions will be added
later.
<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>