VBBS Documentation -- 5-1

	 ����������������������������������������������������������������ͻ
	 � CHAPTER FIVE      MULTI-NETWORKING                             �
	 ����������������������������������������������������������������ͼ

	 MULTINETWORKING
	 ���������������

	      Virtual BBS (TM) software is one of the few programs
	 available capable of handling multiple networks and multiple
	 network types.  In addition, this multinetworking software
	 if capable of functioning as a gateway between networks --
	 even networks of different types.

	 GENERAL
	 �������

		In order to use the multi-networking features, you will
	 need to have the following programs: (Which VBBS will utilize
	 automatically.)

	 VXY                    VBBS Xmodem, Ymodem, Zmodem Driver
	 DSZ                    DSZ External Protocol Driver
	 PKZIP and PKUNZIP      PKware ZIP Archive Utilities

	 MULTINET MASTER LIST
	 ��������������������

		The master list of allowable networks is a file named
	 NETWORKS.LST, and is located in the VBBS Data Directory.
	 This master list is the only way for VBBS to identify the origin
	 and destination of posts and email, 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
	     4,4,FIDOnet
	     9,3,Internet

	 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.

					   VBBS Documentation -- 5-2

	 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.

	 NETWORK-SPECIFIC INTERFACES
	 ���������������������������

		As of this moment, four basic network interface types
	 may be used in conjunction with the VBBS MULTINET ENGINE:

	    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)

	       VNET.EXE and VUUCP.EXE are Virtual ComTech International,
	 Inc.-produced/licensed products, and are included with your purchase
	 of Virtual BBS (TM).

	 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.

		For more specific information about VNET.EXE, see chapter
	 6.  For more specific information about VUUCP.EXE, see chapter 7.
	 For more specific information about setting up third-party
	 utilities, see the documentation that comes with the utility.

					   VBBS Documentation -- 5-3

	 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 and FIDOnet-type networks do NOT
	 need to be configured in ANSWER.NET since type 1 and type 4 networks
	 are automatically detected.  However, to detect types 2 and 3, 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.

					   VBBS Documentation--5-4

	 ?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 Internet via UUCP:
	 >UUCP
	 !
	 ?85=5

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

	 YOUR OWN WIDE-AREA NETWORK
	 ��������������������������

		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.  You can
	 make your network public, or private -- with complete security.

					   VBBS Documentation--5-5

	 GATEWAYS
	 ��������

		VNET also is able to handle email to other networks
	 quite handily, even if your bbs is not actually on a
	 network.

		For example, assume 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 and 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.

		If permission is granted, manually create a text file