home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
CEL141.ZIP
/
CEL141C.ZIP
/
NODEMAN.ZIP
/
NODEMAN.DOC
next >
Wrap
Text File
|
1991-11-05
|
4KB
|
77 lines
Celerity BBS
~~~~~~~~~~~~
Node Manager
The Celerity Node Manager allows sysops to set up their own networks
independent of CelerityNet, which may be more effective and efficient for a
group of boards interested in having only a limited local network. It should
be noted that other CelerityNet-compatible software packages (Havok,
Silicosis, ADI, Faq, and ultimately Vision-X and Velocity) can also be nodes
on these networks.
These smaller networks will not require a dedicated line for network
calls only, like CelerityNet has,because they are limited to a much smaller
size, and will almost always be hosted by a regular Celerity BBS. As
CelerityNet has over fifty connected systems, independent networks have an
upper limit of 6 systems (5 nodes plus the host).
To set up your system as a network host, follow these instructions:
1: Have a Celerity system running completely without problems. Know the
system and its idiosyncracies well.
2: Sit down and plan which subs you wish to carry on your net. Make a list
of the sub names, whether they are to be private subs or not, and then
assign net ID numbers. It is recommended that you use net ID's in
accordance with those currently used by CelerityNet, to ease in any
transition to and from your net and the larger CelerityNet. Scatter your
ID's throughout the unused range so they are not easily hacked. The
unused range is from 50-89 and 95-120. Reserve sub #255 for private
network email.
3: Set up the subs you have decided to create on your system. If you wish,
you can scatter them throughout seperate conferences. If there is a sub
you wish your net to carry, but do not want it on your personal system,
just place it in a conference not accessible by regular users or give it
a high access level.
4: In your setup, turn on the Net Host option.
5: Run the Node Manager, NODEMAN.EXE, to set up the nodes of the systems
participating in the network. Each node is required to have a network
node ID and a password. The BBS name and phone number are optional.
6: Everything should be functional. Do some test net calls to make sure
everything is working correctly.
It should be noted that CelerityNet, with all of its features and
restrictions, may become obsolete within the next six months. Celerity will
most likely continue to support it for a time, but there are a few diverging
paths which networking with Celerity will take:
1: FidoNet. Currently under alpha testing, a FidoNet tosser will allow
Celerity to operate with various front door programs to send and receive
FidoNet messages through national-level PD networks and local networks.
FidoNet is supported by many BBS programs, but is faced with some
severe limitations.
2: HermesNet (working title). Currently under development, a new network
standard is being developed by the authors of Celerity, ADI, and Velocity,
with a few other packages expected to adopt the specification upon its
completion. HermesNet will fully support a Host/Hub/Node structure, so
systems may call regional hubs for lower phone costs (at the cost of
slower responses to email and messages), local networks (a hub may set up
a set of local/regional subs), private subs, and more.
If you or someone you know is active in the development of a BBS program,
and are interested in helping to develop HermesNet, please contact Extreme
A.I. or The Byter via CelerityNet or ADINet.