Category : BBS Programs+Doors
Archive   : VBBS61A2.ZIP
Filename : MULTINET.DOC

 
Output of file : MULTINET.DOC contained in archive : VBBS61A2.ZIP











ÛÛ¿ ÛÛ¿ ÛÛÛÛÛÛÛÛ¿ ÛÛÛÛÛÛÛÛ¿ ÛÛÛÛÛÛÛ¿
ÛÛ³ ÛÛ³ ÀÛÛÚÄÄÛÛ³ ÀÛÛÚÄÄÛÛ³ ÛÛÚÄÄÄÄÙ
ÛÛ¿ ÛÛÚÙ ÛÛÛÛÛÛÛ³ ÛÛÛÛÛÛÛ³ ÛÛÛÛÛÛÛ¿
ÛÛ¿ÛÛÚÙ ÛÛÚÄÄÛÛ³ ÛÛÚÄÄÛÛ³ ÀÄÄÄÄÛÛ³
ÛÛÛÚÙ ÛÛÛÛÛÛÛÛ³ ÛÛÛÛÛÛÛÛ³ ÛÛÛÛÛÛÛ³
ÀÄÄÙ ÀÄÄÄÄÄÄÄÙ ÀÄÄÄÄÄÄÄÙ ÀÄÄÄÄÄÄÙ
*

The Virtual BBS/NET
Version 6.10

Copyright (C) Roland De Graaf 1990, 1991, 1992, 1993

4246 Elisabeth Ave.
Holland, MI 49424

*
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Multi-Network Documentation
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edited By: UT Prof aka Richard Shell 1@2103 VirtualNet
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TABLE OF CONTENTS
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


(1) - THE VBBS MULTINET ENGINE
1.1 - Overview
1.2 - The Multinetwork Master List
1.3 - The Multinet Mail Tosser
1.4 - Network-specific Interfaces

(2) - CONFIGURATION
2.1 - VConfig
2.2 - Answer.net Configuration

(3) - STARTING YOUR OWN NETWORK
3.1 - Considerations for Wide-Area Networks
3.2 - Local Networks

(4) - TECHNICAL NOTES
4.1 - NETWORKS.LST File
4.2 - Net.x Files
4.3 - .NET Files
4.4 - The MultiNet Tosser Functions & Email Gating

APPENDICES
I. Local Network Configuration
II. VFido Configuration
III. VWW4 Configuration
IV. VUUCP Configuration


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
(1) - THE VBBS MULTINET ENGINE
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1.1 - Overview

VBBS is the first BBS program to incorporate a true
multinet engine within the BBS itself, capable of seamlessly
integrating up to 999 networks and providing automatic gating
of e-mail between different networks. The multinet engine
works through the interraction of four components: the
multinetwork master list which identifies the networks,
the multinet mail tosser which processes e-mail and posts,
specific network utilities used for interfacing with each
basic type of network, and the front end mailer which
identifies incoming network calls.


1.2 - The Multinetwork Master List

The master list of allowable networks is a file named
NETWORKS.LST, and is located in the VBBS 'Data' subdirectory.

This master list is the only way for VBBS to identify the origin
and destination of posts and e-mail, so it is a requirement
that major networks be listed in the NETWORKS.LST file.

The NETWORKS.LST file is an ascii file in following format:

1,1,VirtualNET
2,2,WWIVnet
3,2,WWIVLink
4,4,FIDOnet
5,3,USEnet

The NETWORKID comes first, followed by the NETWORKTYPE,
and finally, the NETWORKNAME.

To view the network entries in the NETWORKS.LST file, simply
choose option 7, Network Configuration, on the VConfig menu.

1.3 - The Multinet Mail Tosser

The multinet mail tosser is built directly into VBBS.
No external mail tossers from third parties are needed,
although VBBS can be configured to use them if desired.

The tosser handles this process of distributing email
and posts to the appropriate "pending" files for each
network you are connected to. The tosser also handles
the importation of incoming email and posts to the BBS,
and the gating of posts between networks.

Mail tosser operation is completely automatic and requires
no special attention. Tossing may also, however, be invoked
by command line switches or batch files called by external
events to add flexibility. Please refer to the individual
documentation for each network-specific interface for
details on syntax and how this is accomplished. Such
documentation is included in the zip file for each interface
utility.


1.4 - Network-specific Interfaces

As of this moment, four basic network interface types
may be used in conjunction with the VBBS multinet engine.
These are as follows:

VNET.EXE for VirtualNET-type networks (type 1)
VWW4.EXE for WWIVnet-type networks (type 2)
VUUCP.EXE for UUCP-type networks (type 3)
VFIDO.EXE for FIDO-type networks (type 4)

These utilities may be downloaded from any VBBS support
board and are accompanied by specific installation
instructions.

Please note that these utilities are not crippled in
any manner, however, you should register VBBS within sixty
(60) days to avoid an interruption of service. Failure to
register will inactivate all interface utilities automatically,
with the exception of VNET.EXE, after the 60-day period.
To avoid any inconveniences, please register VBBS as soon as
possible.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
(2) - CONFIGURATION
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

2.1 - VConfig

The multinet configuration is done by running option 7, Network
Configuration, in VConfig. From the net configuration menu, you
simply choose which network you want to add, and enter the
appropriate information. It is very important to remember after
running option 7 to select option 3, Database Configuration,
and run the Sort Databases and Compile Network functions found
there.

For specific installation details, please refer to the main
VBBS560.DOC, and the DOC files that accompany each network
interface utility, ie. VWW4, VUUCP, and VFIDO.

2.2 - Answer.net Configuration

ANSWER.NET, an ordinary ascii text file, should be created
and placed in your VBBS 'Data' subdirectory if you are to
interface with other networks successfully. You must have
answer.net set up properly for VBBS to be able to correctly
identify incoming network calls. In many cases, the incoming
network call will use a macro to identify itself. The
answer.net file is used by the multinet engine to
acknowledge the network macro, identify the network, and call
up the proper network interface utility after connecting.

Note that VirtualNET type networks do NOT need to be configured
in ANSWER.NET since type 1 networks are automatic. However,
to detect types 2 through 4, you must "program" ANSWER.NET to
be able to identify the incoming network from the string it
sends.

ANSWER.NET uses only three simple one-character commands: ">",
"!", and "?".

">" Sends a string. For example, >HELLO would transmit
HELLO

"!" Waits up to 2 seconds for a byte to come in

"?" Compares received byte to ascii code values
and calls up the appropriate network interface driver

Here are some examples:

?78=2
If received byte was 78 ("N"), then answer network #2 (WWIVnet)
N N N N is the string that WWIVNet sends.

?76=3
If recevied byte was 76 ("L"), then answer network #3 (WWIVLInk).
L L L L must be the string that WWIVLink sends and must be set
up by your Link server using a macro.

Here is an example ANSWER.NET, for a VBBS that is on WWIVnet
only which you may use:
!
?78=2
?32=2

Here is an example you may use if you are on both WWIVnet and
WWIVLink:
!
?78=2
?32=2
?76=3

Here is an example for a VBBS on USEnet:
>UUCP
!
?85=5

Here is an example for a VBBS on USEnet, WWIVnet, and WWIVLink
which may be used:
>UUCP
!
?78=2
?32=2
?76=3
?85=5

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
(3) - STARTING YOUR OWN NETWORK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

3.1 - Considerations for Wide-Area Networks

Because of VBBS' uniquely-designed multinet engine, starting
your own new network is easier than ever before whether you
are a business or an advanced system operator. Here are just
a few things to consider if you are contemplating this:

A) You will need to decide on what type of network software
you want to use for your new network:

VirtualNET type
WWIVnet type
FIDO type
UUCP type

While the multinet engine will easily handle any type above,
remember that the simplest network to run operationally is a
VirtualNET type network. This requires no special setup of
the answer.net file or macro setup on the part of the server,
has support for update utilities, and other advantages.

B) You will need to select a name for your network.

C) You will be responsible for maintaining your network, such
as producing its bbslist or nodelist, establishing
connections, nominating ACs, etc.

D) You should have the following thought out in advance:

Network Policy and Goals
Network Application
Advertising
Administration

E) Update utilities

Update utilities let you, as network coordinator send out
BBSLISTs and SUBSLISTs for the maintenance of your network.
Custom update utilities for VirtualNET type networks are
available from the VBBS author. For more information on how
to start a VirtualNET type network, please refer to the
LOCALNET.DOC file.

F) Inclusion in NETWORKS.LST

Since you can edit NETWORKS.LST yourself, inclusion isn't
a major problem. However, we do try to maintain one
"unofficial" networks master list.

3.2 - Local Networks

It is an established de facto standard that local nets
should use slots 15 and 19, in order for maximum compatibility
with everyone else on the planet.

It is highly recommended that if you wish to use a NETWORKID
other than 15 or 19, you should consult the unofficial
networks master list for a unique NETWORKID to use.

Please refer to the LOCALNET.DOC for more details.


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
(4) - TECHNICAL NOTES
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

4.1 - NETWORKS.LST File

The NETWORKS.LST file is a master list of networks. Each
network is defined by Proper Name ("VirtualNET",
"WWIVNet", "USENet",etc.) and by Network Protocol
(VNET, VWW4. VUUCP, VFIDO,etc.), and by Network ID.
Each network must have a unique ID number. IDs begin at
1 and go up sequentially.

4.2 - NET.x Files

These are the configuration files for each network and
are located in the Data subdirectory. The .x refers to
the network ID number as defined in the NETWORKS.LST file.
These are simple ascii files in this format:
=

A NET.2 file for WWIVNet, for example, might look like
this:
systemid=2067
netdir=c:\wwiv\data
mode=net

where systemid is the WWIV node number, netdir is where
the network files are located, and mode is either
"net" or "link" which instructs VWW4 of the mode to run in.

A NET.1 file for VirtualNET, might look like this:

systemid=2103
netdir=c:\vbbs\net
server=1
client=2112 $1-512-340-2265
client=2115 +381-0031 /25

where $,+, /,!, and ^ are optional modifiers indicating
long distance phone numbers, local phone numbers, threshold,
macro, and password.

Note that VConfig is used to edit these NET.x files, but
they could be edited manually.

4.3 - .NET Files

These are located in the DB subdirectory and show the
networks a database (message base,sub) is connected to.
These are ascii files that store the sub identifications.
In addition to the .NET file, .QSC, .BIN, and .DAT files
are generated when a database is configured. For example,
the x.NET file for VBBS Forum, a sub gated to WWIVNet, might
look like this:
1=302
2=5275
This is translated as:
network ID 1 (VirtualNET) sub number 302
network ID 2 (WWIVNet) subtype 5275

If this sub were being gated to other networks, additional
lines would be added with the appropriate information.

Note here also that the sub identification can be a number
or a string. This depends only on the net interface's
interpretation of the data.

4.4 - The MultiNet Tosser Functions & Email Gating

The multinet tosser ensures that all gated messages go to the
proper place. An example of the mechanics are as follows:

When a user posts, two copies are written. One goes to the
database itself, and the other goes to SPOOL.NET which is
a temporary file fond in the Data subdirectory. After
the user logs off, the tosser analyzes SPOOL.NET and
distributes the posts to PENDING.x files, where .x is the
network ID. VBBS then checks for PENDING.x files that
might exist and calls up the proper network interface
handler for each PENDING.x file. The net interface program
reads its own PENDING.x file and packs up the messages.

When a net interface program receives a message, it also
needs to write two copies, one to LOCAL.NET which VBBS
unpacks to the databases, and one to either VALIDATE.x
if validation is turned on for the sub, or to
DISTRIB.NET. DISTRIB.NET is similar to SPOOL.NET except
that messages in DISTRIB.NET are redistributed to all
networks except the one it came in on. (SPOOL.NET is
distributed to all networks).

The multinet mail tosser also handles gating of email.
That is, you can send & receive email to a user on a network
of which you are not actually a member.

For example, let's say you wanted to send an email
to someone on FIDOnet, but you're not actually on FIDOnet,
but you are a member of VirtualNET.

Your first step is to find a VirtualNET system
that is also on FIDOnet. (Multinetworked)

Once that is accomplished, email the sysop of that board
and ask if you may use his system to gate email
into the other network. (It's always good to ask first.)

If permission is granted, manually create a text file
in your DATA directory, the filename should be GATEWAY.x
where x is equal to the network id of the network you
want to have a gateway to. In this example, since are target
network is FIDOnet (Network ID = 4), we would create a
GATEWAY.4 file in the DATA Directory. We will put one
line of ASCII text into this file:

@*

is the node address of our gateway system.
is the TRANSPORT NETWORK which will be used
to gate the mail.

For example, if I wanted my FIDOnet gateway to be
@440 VirtualNET, I would make GATEWAY.4, with the line:
@440*1

Another example: I want to email USEnet thru TechNET
(Network ID = 8) system @1000. I would create a GATEWAY.5
file (Network ID = 5 for USEnet), containing the line:
@1000*8

It should be noted that the TRANSPORT NETWORK must
be of VirtualNET type. An email may, however, pass
thru several gateways (no limit), if needed, to get
it where you want it to go. This opens up some very
powerful possibilities.


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-
APPENDIX I - LOCAL NETWORK CONFIGURATION
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

5.1 - Local Network Configuration

First, be aware that two utilities are available, MAKE15.ZIP
and MAKELN.ZIP, which automate much of the process below if
you are starting your own local network.

To set up your own local network, create a separate directory
for the network; for example c:\vbbs\local. All files for
the local network (networkid 15 or network 19) belong in this
directory.

Bbslist.0 contains the network coordinators node information,
while bbslist.1 contains the information for other nodes
connecting to your system. Subslist.net contains the list of
subs and sub numbers for your network -- four digit subs are
autorequestable, and five digit numbers are secured.

Exact format including spacing of these files is critical to
proper localNET functioning, therefore it recommended that
you cut and paste using bbslist.0 and bbslist.1 from
VirutalNET as a template.

After creating your files, you must add the local net in
Vconfig:
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Set up your LocalNET Settings In Vconfig as follows: ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
1. Node Number=1 --Your node number for localNET
2. Net Dir=C:\VBBS\LOCAL --Path path to localNET directory
3. Server=1 --The net server for your localNET
4. Server Phone #:7773333 --Phone # of your localnet server
5. Server Call: Local --Enter [5] to change toggle
from long distance to local
6. Server Threshold: 1 k ---Means your board will call the
server when a minimum of 1k of
messages are ready to be sent
7. Server Macro:
8. Server Password:
9. Server Protocol: DSZ Zmodem --Must be uniform throughout
your network
A. Server Compression: PKZIP 1.10
C. Add New Client
E. Edit Clients
U. Uninstall this Network

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Add additional nodes (Clients) to your network as follows:³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
-==-

1. Client Node Number: 2180 ---Clients Node Number that you
assigned
2. Client Phone #: 773-8330 ---Clients phone #
3. Client Call: Local ---It is a Local call
4. Client Threshold: 0 k ---Never call out, implying
the client will call you
5. Client Macro:
6. Client Password:
7. Client Protocol: DSZ Zmodem
8. Client Compression: PKZIP 1.10
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Name Your Network ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
Creating a file called DEFINE.NET in your main VBBS data
directory will give your network the name you choose. Type
copy con define.net, then add the name of your choice on the
first line. Hit ctrl Z to save and exit.

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Compiling your network: ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
From your vbbs directory: type the following and press your
enter key: VNET /A NETWORKID=15 (or 19)
You will see the network compile and list the nodes if your
setup is correct.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
APPENDIX II - VFIDO CONFIGURATION
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Introduction
============

This program is designed to create an interface between the
VBBS software written by Roland de Graaf and any Fido-
compatible network. FidoNET itself is the largest hobbyist
network in the world, with over 21,000 BBS members, and
literally thousands of smaller Fido-compatible networks
worldwide.

This version of the interface program allows the exchange of
private mail and public message areas between VBBS and Fido.
VFIDO is fully-featured and has provisions for incoming and
outgoing Crash Mail, File Requesting, and File Attaches as
well.

Used in conjunction with the integral VBBS front end mailer
or with FrontDoor, VFIDO readily handles calls to and from
other Fido BBSes running VBBS, FrontDoor, BinkleyTerm, or
other mailers adhering to FidoNet FTS-0001 specifications.

Joining FidoNET
===============

Until the arrival of VBBS, setting up FidoNET for the first
time was a laborious and complicated chore for sysops
unfamiliar with Fido's idiosyncrasies. In essence, FidoNET
policy requires the sysop to have his interface software set
up properly before he can officially apply for a FidoNET node
number. Application for a node number must be made through
e-mail sent from the requesting sysop's bbs through FidoNet
to the local Area Coordinator. A temporary node number is
issued by the AC for the sysop to be able to make this
connect. This procedure may vary from area to area, however,
so please contact the nearest AC for information.

Before proceeding with VFido installation, then, you must
first obtain a provisional node number from your local
FidoNET Area Coordinator and information about what
application information you need to provide him with. Using
the provisional node number the AC issues you, you may begin
installing the VFido interface. After this initial setup is
completed using this temporary node number, you must send
the application information directly to the AC in Fido email.
The direct connect from your BBS via Fido is the AC's
guarantee that your bbs software has been set up correctly
and is Fido-capable.

Based on the application information you email, the AC will
then issue you an official FidoNET node number and begin
proceedings to have your number listed on the main FidoNET
Nodelist. At this point, you will have to update the FidoNET
network information (option 7 in VConfig) in VBBS to
replace the provisional node number used for the initial
connect with your official and permanent node number.
The information entered in VConfig must be recompiled (see
below).

Normally, you may expect to wait 5-10 days for your new Fido
node number to appear on the official Fido Nodelist, at
which point you may begin subscribing to echoes,etc.


Initial Configuration Of VFIDO To Give E-Mail Functionality
===========================================================

Place the VFIDO.EXE program in your VBBS directory.

Run VCONFIG.EXE, and select Network Configuration for the
Fido (type 4) network you are configuring.

1. Fido Address: 2:440/211
Your Fido network primary address in Zone:Net/Node.Point
format)
2. NetMail Directory: C:\VBBS\NETMAIL
Where Fido netmail will be stored - must be the same for
all your Fido networks
3. OutBound Directory: C:\VBBS\OUTBOUND
Where Fido EchoMail will be stored - must be the same for
all your Fido networks
4. Archiver: PAK
Compression method for outgoing EchoMail - PAK, LHA, ZIP,
ARJ
5. UnArchiver: PAK
Compression method for incoming EchoMail - PAK, LHA, ZIP,
ARJ
6. FIDO Front-End: Standalone
Standalone or FrontDoor are only valid options at this
stage
7. Nodelist Name: NODELIST
The name of the nodelist for the network
8. Zones: 1-7
The range of Zones that belong to that network (ie the
Domain)

D. Dial List

1. System Address: 2:440/59
Fido address of node to call
2. Phone Number: 0689-824890
Full phone number to dial
3. Poll Priority: Hold
Hold means never call, Priority is call as soon as mail
is waiting, once a day is the final option
4. Preferred Session Type: EMSI (FSC-0056) w/Zmodem (DSZ)
EMSI or TSYNCH handshaking selection
5. Session Password: FRED
The password to use in the EMSI session with the other
BBS, which may be blank

R. Routing

1: 2:440/59 2:440/59
Fido address of server and routing mask including
wildcards. The routing logic works top to bottom through
this list so you can't add anything meaningful after the
last line with the *:*/* on it.
2: 1:1/1 1:*/*
3: 2:440/6 *:*/*
A)dd Lines E)dit Lines D)elete Empty Lines Q)uit:

A. AKAs

1: 2:440/59.3
Alternative address for the board - must be same Zone
2: 2:440/0
A)dd Lines E)dit Lines D)elete Empty Lines Q)uit:

Once this configuration is completed, go to the main VBBS
directory and run:

VFIDO /C NETWORKID=#

You must rerun this every time you change any of the above
configuration information.


VFido Control File
==================

You will also need to set up a file containing phone prefix
aliases called VFIDO.FON in your DATA subdirectory. This is
used to ensure that the phone numbers listed in the nodelist
are converted to a format that can be dialed from your BBS.
This is used for removing your country code for national
calls and area code for local calls. VFIDO needs the correct
phone numbers listed so it can call any BBS in the nodelist
when Crash Mail, File Attaches or File Requests are sent.

An example of this control file for the USA would be:

011- The prefix for dialing international phone
numbers
1-616-399- 399- Sets up the toll free codes for your area
code, where 616 is the area code and 399
a local prefix
1-616- 1- Makes all other calls in your area code long
distance
1- 1- Ensures all US phone numbers are not made
international

This example would convert a phone number listed as
1-616-399-4818 to 399-4818, or convert 1-616-772-0482 to
1-772-0482, or 44-689-890937 to 011-44-689-90937

and for Europe:

010- The prefix for international calls
44-689- Strip the country and area code for local
calls
44- 0- Add a 0 prefix for national calls

As an example, the above would convert an international
phone number listed in the nodelist as 1-616-399-4818 to
010-1-616-399-4818, or a national number in the nodelist as
44-689-890937 to 0-689-890937.


Nodelist Compilation
====================

Obtain the most recent nodelist from your FidoNet server
and place it unarchived into the C:\VBBS\NETMAIL directory.
Then at the prompt in the main VBBS directory type:

VFIDO /A NETWORKID=#

You will need to rerun this every time you receive a new
NODELIST, or when you change information in the VFIDO.FON
control file.

Since the FidoNET nodelist is quite large, normally your
Netmail Server will only send out weekly updates called
NODEDIFF files automatically. Third party utilities such as
XLAXDIFF and MERGENL may be used to make a new updated
nodelist using the NODEDIFF information. After doing this,
the above analysis must be run.

Batch files have been developed which automate this updating
process and can be called up in daily maintenance. Here is
an example of one such batch file which checks to see if
there is a NODEDIFF file and uses the XLAXDIFF utility to
produce a new NODELIST.

@ECHO OFF
IF EXIST C:\VBBS\OUTBOUND\NODEDIFF.* GOTO :GOTONE
GOTO :EXIT
:GOTONE
CD C:\VBBS\NETMAIL
DEL NODEDIFF.*
CD C:\VBBS\OUTBOUND
COPY C:\VBBS\OUTBOUND\NODEDIFF.* C:\VBBS\NETMAIL\NODEDIFF.*
DEL NODEDIFF.*
CD \VBBS\NETMAIL
XLAXDIFF /C
CD \VBBS
VFIDO /A NETWORKID=4
:EXIT
ECHO NO NEW NODEDIFF FILE TO UPDATE!
EXIT


Sending E-Mail Using VFIDO
==========================

To send an E-Mail message from VBBS to any Fido-type network
, invoke the E-Mail routine as normal. The User Network
Address field should be completed in the format User
Name@Fido Address, so to send E-Mail to me use Neil J
Marshall@2:440/211.

If you want to send Crash Mail, that is where the E-Mail is
sent directly to the addressee's BBS, ignoring the routing
logic, then add a " +c" after the addressee's name, so to
send Crash Mail to me use Neil J Marshall +c@2:440/211.

In Fido-type networks it is policy that messages with files
attached must go directly to the addressee's BBS and ignore
the routing logic, so if you attach a file to a message it
will be held on your board awaiting a call from the
addressee's BBS unless you send it Crash Mail or the
addressee is one of the BBSs in your dialing list that you call.


File Requests Using VFIDO
=========================

If you want to send a File Request to another Fido-type BBS
invoke the e-mail routine as normal. The User Network
Address field should be completed in the format
Sysop +f@Fido Address, where the " +f" is the switch to
indicate this is a File Request. The Filename requested is
put in the Title field of the message. All File Requests are
sent direct to the addressee's BBS and ignore routing. If the
addressee's BBS is not one that you have set up in your
dialing list, then you must also use the +c switch to make
the File Request a Crash E-Mail. To request the latest
version of VFIDO from me, you would invoke the E-Mail
function and address it to Sysop +f +c@2:440/211, then make
the Title of the message VFIDO.

VFIDO also supports incoming File Requests. When a File
Request is received, VFIDO searches each of the File Areas
that you have set up in VCONFIG and sends the file back if
it is found. VFIDO also supports "Magic Names" for File
Requests - this is where a pseudonym is associated with an
actual file for ease of access by calling systems.
Magic Names should be set up in the file VFIDO.MAG in your
DATA directory. The format of this file is one entry per
line, giving the "Magic Name" followed by the full path and
filename of the file to associate with the Magic Name, for
example
VBBS C:\VBBS\FILES\SYSOP\VBBS560.ZIP
FILES C:\VBBS\MASTLIST.TXT
VFIDO C:\VBBS\FILES\SYSOP\VFIDO560.ZIP
might be some of the most common ones.

If you want a "standard letter" sent in response to each file
request, create this letter in a file called FILEREQ.TXT in
your TEXT path. Generally a Fido Sysop should use this to
list the Magic Names applicable to their BBS.


Configuration Of VFIDO To Add Conference Functionality
======================================================

If you want to access public message areas in Fido, you will
need to know the AREA name that uniquely identifies each
Fido conference. Supposing for example you wished to set up
VBBS to participate in a Fido conference whose AREA name was
HARPOON:

Run VCONFIG.EXE and select Database Configuration, Message
Bases, the relevant Group and Database. Then select Networks
Configuration, A for add, select the network, and on the line
for the Network Conference Identifier, put the AREA name of
the Echomail conference in the network, and ALSO, separated
by a space, the Fido addresses of the nodes to whom you
directly circulate the conference, if you are acting as a
local hub. If you are simply receiving a conference, then
place the node number of the EchoMail server you connect
with to obtain the conference after the AREA name.

This line is currently limited to 80 characters here so it
will be difficult for you to become a major hub yet. Our
plans do call for amplifying this field shortly, however.

An example of the FidoNET entry in the database would look
like this:

Network Conference Identifier: HARPOON 2:440/59 1:2/3
^ ^
* *
* *
* These are the Fido
* addresses of the BBSes
* in the circulation list
* (or Echomail server of
* the conference)
*
This is the AREA name of the Fido
conference

After you have set up all your conferences, you must run
VCONFIG, Database Configuration, Compile Network
Configuration - and you will have to rerun this every time
you change the network configuration of a database.

With these simple steps taken, every message posted on that
conference will be echoed to Fido, and every message from
Fido on that conference will be fed into VBBS.


Using AreaFix To Request Conferences
====================================

You can add or remove your BBS to the subscription list for
conferences on other Fido BBS using AreaFix.

All you have to do is to send a NetMail to AreaFix at the
BBS address with your AreaFix password as the title (the
AreaFix password is agreed in advance by yourself and the
other Sysop) and a content that lists, line by line, the
Area name of a conference, preceded by a - for remove.

For example, a message whose content read:

VFIDO_SUPPORT
-GAMES_DISCUSSION
-------

would add your BBS to the VFIDO_SUPPORT conference and remove
it from the GAMES_DISCUSSION conference. The ---- tear line
is used to indicate to AreaFix the end of your requests.

VFIDO supports incoming AreaFix requests as well. However,
there is no facility for implementing an AreaFix password,
so the title of the NetMail can be anything.


Summary Of VFIDO Command Syntax
===============================

VFIDO {channel number} {option} NETWORKID=#

# is the network identifier as specified in the NETWORKS.LST
file for the network you are connecting to.

{channel number} is only necessary with /DIAL, /HOST
and /POLL options.

{option} is one of:

/A Build network list from nodelist
/C Compile initial Fido information
/DIAL Make a call to another Fido address, specifying the
address right after the switch like /DIAL2:440/211
/HOST Answer an incoming Fido call
/POLL Call all systems for whom Crash Mail is pending
/U Scan VBBS mail and toss to Fido
/T Scan Fido mail and toss to VBBS

For example, a batch file to call up from the WFC to force
Crash Mail callouts might contain something like this:

VFIDO 1 /POLL NETWORKID=4

Technical Information
=====================

VFIDO creates FTS-0001 packets for NetMail with FSC-0039
extensions for Zone and Point 4D addressing, FTS-0004 ARCmail
packetsfor EchoMail, and FTS-0006 WaZOO-format File Requests.

Connections can be using FTS-0001 (TSynch) using XMODEM or
FSC-0056 (EMSI) using ZModem.

Outgoing Crash Mail is only supported using EMSI.


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
APPENDIX III - VWW4 CONFIGURATION /WWIVNET AND LINK SETUP
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Requirements
------------

It should be pointed out here that in order to interface VBBS
with WWIVNet and WWIVLink (or other WWIVtype networks), you
should register VBBS as soon as possible. Multinet access in
the shareware version is limited to 60 days, after which time
all network interface utilities with the exception of VNet,
become inoperable. By registering, you are guaranteed that
network access will not be interrupted, so please do register
VBBS as soon as possible to avoid any inconvenience. There
is a only a one-time, life-time registration fee for the DOS
version of VBBS.

VWW4.EXE is the interface utility designed especially for VBBS
version 6.10 which carries out the net interface function for
all WWIV-type networks, including WWIVNet, WWIVLink, and
ICENet. Before setting up the interface, however, you should be
aware that many subs from these networks are now being gated to
VirtualNET. Thus, it may not even be necessary for you to carry
out this interface at all. Please read the NETGUIDE.DOC for
information on how to set up and join VirtualNET and subscribe
to subs. A current SUBSLIST.NET file in your NET subdirectory
lists the various subs available to choose from.

Now, if you already have VWW4.EXE in hand and want to continue
with the interface installation, be aware that you MUST also
have a WWIVnet or WWIV-type node number in order to net. You
must also set up the appropriate WWIV network files according
to instructions from your AC/GC.

WWIVNet network policy has changed recently and sysops are
required to register the WWIV network software within 60 days.
After this period of time, unregistered sysops are
automatically dropped from the WWIV bbslist. The WWIV network
files may be registered separately for $20, and we urge all
sysops that wish to have access to all WWIV-type subs to
register this software. Contact your local WWIV AC for more
information. As for WWIVLink sysops, no such registration
requirement currently exists and separate network software is
available.

In general, it is best to set up WWIV completely and separately
until your net connects are operational. It is easier then to
delete the unnecessary WWIV files later. If you plan on
receiving more than one WWIV-type network, then you should set
up individual WWIV directories with different directory names,
and realize your net connections first before making any file
deletions. This procedure is covered thoroughly in the WWIV
install documentation and in the network documentation written
by WWIV support staff. It is important that your net
connections be properly established and each WWIV bbs be
fully functional in this respect before proceeding. It is also
recommended that all net connections through VWW4 be made using
Channel 1 selected in VCONFIG (option 2), although any active
channel may be used.

Initial Configuration
---------------------

Once you have established normal net connections through WWIV,
then proceed as follows:

Step 1 - Run VCONFIG once again and choose the NETWORK
configuration option (option 7).
Here you will see a list of current networks handled
by the multinet engine. Choose WWIVNet (or WWIVLink,
etc) with the up/down arrow keys and fill in the
appropriate fields shown below. Please note that each
network listed has a separate slot in the NETWORKS.LST
control file and that all WWIV-type networks are Type 2,
meaning they use VWW4 as the interface utility.

You will now see the following type of screen:

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Network #2 WWIVnet Type 2 (VWW4.EXE) ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

1. Node Number:
2. Data Directory:
3. Mode:
4. EXE Directory:
5. Dialout Init String:

U. Uninstall this Network

Step 2 - Enter your WWIVnet node number in the first field.

Step 3 - In the next field, enter the full path to the WWIVNet
DATA directory (e.g. c:\wwiv\data).

Step 4 - For Mode, select NET for WWIVNet-type networks, or
LINK for WWIVLink-type networks.

Step 5 - For the entry to the EXE (executeable) directory,
specify the complete path to where the WWIV network
executeable files are located (e.g. c:\wwiv).

Step 6 - For your Dialout Init String, leave this blank for now,
unless you are using a version of WWIV prior to WWIV
4.20. Later on when testing your WWIV connect with the
multinet engine, it may be necessary for you to include
the WWIV modem init string in this space if you fail to
connect properly. This string would be the same one
chosen from the WWIV modems.mdm file. Again, make sure
you connect properly to your WWIV server independently
from VBBS before attempting the interface here.

Step 7 - After Vconfiguring the NETWORK option above, unzip the
VWW4.exe file in your root VBBS directory and read the
technical information given in the VWW4.DOC . It should
be noted that the multinet engine in VBBS 6.10 is
automatic and requires no batch files, but batch files
may be used for convenience and flexibility depending
upon your setup.

Step 8 - You must now create an ANSWER.NET file based on the
information provided in the MULTINET.DOC file. This
should be placed in your VBBS DATA subdirectory.

For a VBBS that is on WWIVNet, the ANSWER.NET file
would look as follows:

!
?78=2
?32=2

For a VBBS on WWIVNet and WWIVLink, the ANSWER.NET
would contain:

!
?78=2
?32=2
?76=3

Please refer to other parts of the MULTINET.DOC for
more details. Just as an explanation, the ?78 above
refers to the N N N sign that WWIVNet sends as an
incoming identifier. The ?76 is an L L L that WWIVLink
uses. These are ascii characters 78 and 76,
respectively.


Step 9 - Copy NETWORKS.LST from the zip package to the VBBS NET
subdirectory.

Step 10 - If you are interfacing with both WWIVnet and WWIVLink,
you MUST maintain separate directories for NET and
LINK as mentioned previously. The same holds true for
any other WWIV-type networks you subscribe to. In each
directory make sure that all of the WWIV network files
are in their proper places. Make sure you have run
Vconfig's Network option and set the path correctly
to where the respective networkx.exe files are
located.

NOTE :

You will also have to maintain the DATA subdirectories in each
of these to create the necessary NNxxxx.net and Nxxxx.net
or NNALL.NET files needed later to subscribe and to host subs
on WWIVNet. If you are converting totally over to VBBS from WWIV
and would like to delete unnecessary/unwanted WWIV files, a list
of the required WWIV files may be found in the APPENDIX. Erasure
of unwanted files, however, should be the very last step you
take in the conversion process after verifying successful
net connections. As an alternative to deletion, we suggest that
you simply zip up the unnecessary files and keep them in a safe
place in the event you need them to reconfigure something in
WWIV itself later.


Step 11- Run VConfig again and choose the Databases (option 3).
Choose Sort Databases to allow the program to set up.
Now choose the Compile Networks option. It is important
to note than whenever ANY changes are made in the
Network option or in Database entries, this must be
followed by the Sorting and Compiling options above
for the changes to take effect.

This complete the network installation procedure.


Installing Message Bases
------------------------

Assuming you have placed VWW4.exe in your main VBBS
directory and vconfigured the networks properly,
then installing a message base is a fairly simple process.
Follow the instructions given in the main documentation
regarding adding databases.

In the database entry for a sub, note that option G is for
Networks Configuration. Choosing this will bring up
a screen which allows you to A)dd D)elete E)dit a
network.

Pressing A) to add a network brings up a screen where you
can choose the appropriate network. For a sub carried on
WWIVNet, you would choose entry 2, for example.

Doing so will bring up another prompt as follows:

WWIVNet Network Conference Identifier:_

Simply enter the subtype number of the message base you
want, and press enter.

Exit out of the database to the main database menu and
once again, choose Sort Databases and Compile Networks.

Please note that if a message base is being gated to
VirtualNET from any other network, you have the option
of subscribing to it as a VirtualNET sub or as a sub
from another network, but NOT both. Doing so will result
in duplicate posts.

NOTE:

If you are subscribing to a Net or Link sub for the first
time, you must follow the normal procedure of requesting
the sub from the host and setting up the appropriate
NNxxx.NET files or NNALL.NET file in the proper data directory.
In addition this version of VBBS also supports WWIV's auto
request sub feature (req.exe) using the VREQ utility available.
It also accepts type 20 messages (subs.pub) using the VWWIV
utility.


Hosting a WWIV Sub
------------------

If you are currently hosting a WWIV message base, be assured
that the same procedure above works for hosts. Again, simply
enter the appropriate subtype when asked for the Network
Conference Identifier. Don't forget that you must maintain your
distribution list through you Nxxxx.NET file as usual. Subs
flagged for validation may be validated from the SysOp SubMenu.


Gating Subs to Other Networks
-----------------------------

If you are currently hosting a sub on WWIVNet or another
network, you probably will be interested in 'gating' your sub
into VirtualNET or other networks to expand your subscriber
base. This is easily accomplished by adding additional networks
to your database entry. Entering more than one network and
respective Network Conference Identifier (subtype, sub number,
echo,area,etc.) effectively 'gates' that database.

NOTE:

If you are running VBBS as a chain, we do not recommend that you
attempt gating due to the mechanics of the multinet engine. If
you wish to gate to multiple networks, we strongly recommend
that you run VBBS as your main bbs software for simplicity's
sake.

Please refer to the NETGUIDE.DOC for further details on how to
set up a hosted VirtualNET sub, sub numbers,etc.


Forcing a Callout
-----------------

Please note that the VWW4 software is fully automatic, and will
callout and receive calls from your server depending upon your
main settings for Threshold and Polling in Vconfig. However, you
most likely will wish to force callouts to your server from
the WFC screen from time to time. To do so, you should Type 'N'
from the Control Panel. First, this will bring up all the
Networks you currently belong to. Select the appropriate network
followed by the appropriate system (server). This will force
the system to call a particular node.

NOTE:

WWIVNet and WWIV-type callouts are completely automated if you
are running VBBS as your main program. Be sure to set your
Threshold level and Polling frequency in Vconfig. Note that the
settings of these levels apply generically to all networks,
(e.g. the same threshold and polling configurations apply to
VirtualNET, WWIVNet, and WWIVLink packets). Setting the
threshold level to 0 effectively tells the software never to
dial out automatically, so be sure to change this. For different
calling schedules, appropriate utilities such as POLLUTIL.ZIP
and VWW4-CHK.ZIP are available to customize your setup.


VWW4 Activity Log
-----------------

All net connections made by VWW4 are also listed in the VWW4.LOG
file which can be found in your main WWIV directory. We suggest
setting up a function key to be able to view this from the VBBS
WFC screen using the Control Panel option in Vconfig. For
example, a bat file called VWW4LOG.BAT could be created and
placed in your VBBS directory with the following command line:

CD\WWIV
VLIST VWW4.LOG
CD\VBBS

If you are interfacing with both WWIVNet and WWIVLink, then a
second batch file similar to the above would need to be created
pointing to your Link directory, and a second function key set
up in the Control Panel.

Viewing WWIV's net logs may be done in the same fashion using
the Control Panel. Simple script mods are also available to view
all pending lists from the internal Sysop Menu in VBBS.


Analyzing the BBSList
---------------------

VBBS creates a listing of systems belonging to various networks
that is used for routing mail. You will need to compile this
information for WWIV the first time you set up so that it may be
viewed from inside of the board. Subsequent updates are made
automatically. Note that when WWIV calls in with new bbslists,
these will be compiled normally and no special maintenance is
necessary.

To make a new indexed list of WWIV boards for use by VBBS,
please delete the existing BBSDATA.IDX file from your WWIV data
subdirectory first. Then, from the WWIV main directory type:
NETWORK3 /Y . This will produce new a new idx file.

Now, generate a new bbslist index for VBBS. Change to the root
VBBS directory where VWW4 is located and type:

VWW4 B NETWORKID=2 for the WWIVNet list, or
VWW4 B NETWORKID=3 for the WWIVLink index

You should now have succesfully created the new bbslist index
file that VBBS uses. This is located in your VBBS Data
subdirectory.

The procedure is similar for generating bbs listings for other
WWIV-type networks. Be aware of the importance of specifying the
correct Network Identifer Number in the above command line
NETWORKID= . Refer to the list of networks available in
VConfig's Network options if you need to refresh your memory on
what network the appropriate network number is.

VWW4 Command Line Switches
--------------------------
The Virtual MultiNet Engine (VME) handles WWIVtype networks
seamlessly. However, VWW4 functions may be called up from batch
files also, thus providing a flexible means for you to customize
your setup.

VME will run the VWW4 as needed automatically, providing the
proper NETWORKID= and PORT= parameters. Running from a command
line, however, you must specify the following three command
line parameters:

VWW4 NETWORKID= PORT=

The command letter tells VWW4 what to do:

Command Letters are:

B Bundle mail for WWIV (Update WWIV packets and bbslists)
U Unbundle mail from WWIV and store in VBBS databases
D#### Dial WWIV System #, do transfer, and unbundle if
successful
A Answer WWIVnet call, do transfer, and unbundle if
successful.

The NETWORKID= parameter tells VWW4 which network to process.
WWIVnet is net #2, WWIVLink is net #3, ICEnet is net #6, and if
new WWIVnet based nets appear, they will have net numbers
assigned to them as well. Check NETWORKS.LST for the current
network list.

The PORT= parameter must be included when using VWW4 to answer,
or dial a network call. This specifies a COM port number.

An example of forcing bundling from the command line would
look like this:

VWW4 B NETWORKID=2 PORT=2

This would bundle the mail for WWIVNet for processing on comport
2.

Please refer to the extended VWW4 documentation included
with the VWW4.EXE file itself for more detailed information
about converting from WWIV to VBBS.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
APPENDIX IV - VUUCP CONFIGURATION AND INSTALLATION
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-




  3 Responses to “Category : BBS Programs+Doors
Archive   : VBBS61A2.ZIP
Filename : MULTINET.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/