Quick Start
Quick Start Guide
CHAPTER 2
This guide provides a step by step checklist for the three most common types
of Dialnet connections. By selecting the type of connection which best represents
your planned use of Dialnet, and then following the checklist, you can bring
Dialnet to an operational state in the fewest number of steps.
Before continuing with this section you should be familiar with TCP/IP,
wide area networking, and basic routing strategies, If you are not familiar
with these concepts Chapter 4 of the manual is a TCP/IP Networking Primer.
The primer has three sections directly related to using Dialnet in a wide
area network, They are:
The IP Level - How datagrams are forwarded to the remote computer,
Routing - How gateways forward IP datagrams.
Details about Internet addresses - How Internet addresses are selected and
used,
Common Uses of Dialnet
Connecting Networks - One of the most common uses of Dialnet is to establish
wide area network connections between local area networks at geographically
dispersed sites. The diagram in figure 2-1 shows this configuration.
Dial-ln Hosts - Dialnet can be used for individual hosts to gain access
to their central network. This is common for UNIX Workstations, or PC's
which support TCP/IP and the SLIP protocol. These are typically used for
home systems (ie. te]e-commuting) or for portable systems which need dial-up
access to electronic mail or network file transfer. The diagram in figure
2-2 shows this configuration.
Hardwired Connections - Either of the previous types of connections can
be configured to run over dedicated leased lines. In this mode, it may be
desirable to eliminate dialing and login security steps and assume a direct
connection is always available. This mode of operation also decreases the
configuration requirements for the connection.
Each of the above connection types is described in the following three sections.
Proceed to the section which best matches your implementation requirements
and follow the recommended installation steps. If none of these configurations
matches your requirements, use them as a reference and proceed to Chapter
3 "Administration" for a detailed description of each configuration
option,
Connecting Networks
This section describes the steps for connecting two networks together over
dial-up telephone lines for on-demand usage. On-demand means that the PortMaster
automatically dials and establishes the network link when packets are queued
for the remote site. This section assumes that a PortMaster will be used
at each site, and modems which are compatible with each other will be used,
This example can be used for connecting more than two sites together by
simply following the same steps for each site,
Internet Addresses
When connecting two sites which have never directly communicated with each
other using TCP/IP it is important to perform some general internet Address
Administration. The steps for this are:
[] Verify that every computer on both networks has a unique Internet Address.
[] Verity that the network (or subnet) numbers at each site are unique.
If the two locations are using the same network numbers datagram routing
will not work correctly. In this case, one of the networks must be changed.
[] Create a common "hosts" file for both sites so users can access
the computers By the remote location by name. In hosts file, no two computers
should have the same name. Alternatively, Domain Name Service can be implemented.
Check your workstation, or TCP/IP vendor's manuals for information on this
service.
Hardware Configuration
The PortMaster should be connected to the local ethernet network and the
installation steps in Chapter 2 of the PortMaster User's Manual should be
followed. The modem should be attached to one of the ports on the Portmaster
wit a standard modem cable. The modem should also be connected to a direct
dial telephone line.
Every modem manufacturer supports a wide variety of configuration settings.
Experience has shown that the following configuration parameters are the
most important, however the modem manufacturer's manual should be carefully
reviewed if the following parameters are not sufficient, The modem should
be configured as follows:
[] Fixed baud rate (usually the fastest speed the modem will run up to 38,400
baud).
[] RTS/CTS flow control.
C] 8 databits, i stop bit, no parity,
[] Normal carrier detect.
[] Hang-up and reset when DTR drops.
Global Configuration
The PortMaster Global Configuration should be checked. This should be done
using the PMconsole program. See the section on Global Configuration in
Chapter 3 for instructions on editing the global configuration.
[] Routing should be set to "Broadcast".
[] The broadcast address should be checked against the one being used by
other gateways on the local ethernet.
[] Slip should be "Enabled".
Port Configuration
Each Serial port which will has a modem attached, and will be used for Dialnet
connections should be configured. See the section on Setting the Serial
Port Configuration in Chapter 3 for instructions on editing the serial ports,
[] The serial port should be set to "Extended" Mode.
[] The Port Type should be set to "Slip".
[] The Slip Service should be set to "Dial In&Out".
[] If the port will be used for other services (ie, TwoWay) this port type
should be selected in addition to "Slip".
[] The Baud Rates, Modem Control, and Flow Control should be set to match
the modem.
[] The Dial Group should be set to "0" (the default).
Password Table Entry
The Password Table is used for all dial-in connection establishment. A password
entry should be created on the
PortMaster's at each site to establish login security for the remote PortMaster.
Follow the instructions on "Managing the Password Table" in Chapter
3 to set up a new password.
Location Table Entry
The Location Table is used for dialing out from the local PortMaster to
a remote site. A location entry should be created on each PortMaster referencing
the PortMaster (and network) at the other site. Follow the instructions
on "Managing the Location Table" in Chapter 3 to set up a new
location. For testing purposes, the location type should be set to manual
until the dial command script has been properly tested.
Testing
To test a new connection:
[] Attempt to dial from one PortMaster to the other PortMaster using the
Dialer screen. The use of this screen is described in Dialing Out to Remote
Locations in Chapter 3.
O Make any necessary changes to the Dial Command Script and retry dialing
until the connection succeeds.
[] Once the connection is successful verify that the remote PortMaster is
accessible through the network (ie. "ping" the remote PortMaster).
[] Verify that a computer at the remote location is accessible (ie. use
Rlogin, ping, or telnet).
[] Reset the serial port to drop the line and perform the above steps dialing
in the opposite direction.
[] With the serial ports on each PortMaster reset (ie, no active connection)
switch the location types to On-Demand,
Dial-In Hosts
This section describes the steps for enabling dial-in SLIP connections for
remote computers. Users who wish to use this type of connection must have
software on their workstation or PC which allows them to issue dial commands
to their modem, respond to login and password prompts from the PortMaster
for security, and switch over to the SLIP protocol for sending and receiving
TCP/IP datagrams.
Internet Addresses
When connecting a remote computer into the network through a PortMaster,
that computer must be assigned a valid Internet address on the same network
to which the PortMaster is attached. For example if the PortMaster is on
network 192.200.1 and has the internet address 192.200.1.20, the remote
computer should he assigned a free address on the 192.200.1 network (ie.
192.200.1.21).
[] Verify) that the remote computer has a unique Internet Address.
[] Update the global "hosts" file so users can access the computer
at the remote location by name and install the global "hosts"
file on the remote computer. Alternatively, Domain Name Service or Network
Information Service can be implemented. Check your workstation, or TCP/IP
vendor's manuals For information on these service.
Hardware Configuration
The PortMaster should be connected to the local ethernet network and the
installation steps in Chapter 2 of the PortMaster User's Manual should be
followed. The modem should be attached to one of the ports on the PortMaster
with a standard modem cable. The modem should also be connected to a direct
dial telephone line.
Every modem manufacturer supports a wide variety of configuration settings.
Experience has shown that the following configuration parameters are the
most important, however the modem manufacturer's manual ahould be careful~y
reviewed if the following parameters are not sufficient. The modem should
be configured as follows:
[] Fixed baud rate (usually the fastest speed the modem will run up to 38,400
baud).
[] RTS/CTS flow control.
[] 8 databits, 1 stop bit, no parity.
[] Normal carrier detect.
[] Hang-up and reset when DTR drops.
Global Configuration
The PortMaster Global Configuration should be checked. this should be done
using the PMconsole program. See the section on Global Configuration in
Chapter 3 for instructions on editing the global configuration.
[] Routing should be set to "Broadcast".
[] The broadcast address should be checked against the one being used by
other gateways on the local ethernet,
[7 Slip should be *'Enabled".
Port Configuration
Each Serial port which will has a modem attached, and will b used for Dialnet
connections should be configured. See the section on Setting the Serial
Port Configuration in Chapter 3 for instructions on editing the serial ports.
[] The serial port should be set to "Extended" Mode,
[] The Port Type should be set to "Slip".
[] The Slip Service should be set to "Dial In".
[] If the port will be used for other services (ie. User Login) this port
type should be selected in addition to "Slip".
[] The Baud Rates, Modem Control, and Flow Control should be set to match
the modem.
[] The Dial Group should be set to '0" (the default).
Password Table Entry
The Password Table is used for all dial-in connection establishment. A password
entry should be created on the PortMaster to establish login security for
the remote computer. Follow the instructions on '*Managing the Password
Table" in Chapter 3 to set up a new password.
Testing
TO test a new connect[on:
U[ Attempt to dial from the remote computer into the PortMaster. Monitor
the serial port, and the network statistics window using PMconsole during
the login process. The use of this screen is described in Monitoring the
PortMaster in Chapter 3.
Verify that the remote computer has correct routing table entries. This
can be done by creating a default route or using dynamic routing (RIP) to
the PortMaster. Default routes are tile easiest to use and are generally
settable through tile "route" command in UNIX and other implementations,
[] Once the connection is successful verify that the PortMaster is accessible
to the remote computer through the network (ie. "ping" the PortMaster).
[] Verify that a computer at the central site is accessible (ie. use Rlogin,
ping, or telnet).
Hardwired Connections
This section describes the steps for enabling hardwired SLIP connections
for remote computers or networks. Users who wish to use this type of connection
must have a PortMaster at each end of the connection or a Portmaster on
one end and computer on the remote end which supports the SLIP protocol.
Internet Addresses
When connecting a remote computer into the network through a PortMaster,
that computer must be assigned a valid Internet address on the same network
to which the PortMaster is attached. When connecting two sites which have
never directly communicated with each other using TCP/IP it is important
to perform some general Internet Address Administration.
[3 Verify that every computer on both networks has a unique Internet Address.
[] If two networks will be connected, verify that the network (or subnet)
numbers at each site are unique. If the two locations are using the same
network numbers datagram routing will not work correctly. In this case,
one of the networks must be changed.
[] Create a common "hosts" file for both sites so users can access
the computers at the remote location by name. In
hosts file, no two computers should have the same name. Alternatively, Domain
Name Service can he implemented. Cheek your workstation, or TCP/IP vendor's
manuals for information on this service.
Hardware Configuration
The PortMaster should be connected to the local ethernet network and the
installation steps in Chapter 2 of the PortMaster User's Manual should be
followed. The modem should be attached to one of the ports on the PortMaster
with a standard modem cable. The modem should also be connected to a direct
dial telephone line.
Every modem manufacturer supports a wide variety of configuration settings,
Experience has shown that the following configuration parameters are the
most important, however the modem manufacturer's manual should be carefully
reviewed if the following parameters are not sufficient. The modem should
be configured as follows:
[ ] Set the type of telephone line to dedicated leased line.
[] Fixed baud rate (usually the fastest speed the modem will run up to 38,400
baud).
[] RTS/CTS flow control.
[] 8 databits, 1 stop bit, no parity.
[2 Normal carrier detect.
El Hang-up and reset when DTR drops.
Global Configuration
The PortMaster Global Configuration should he checked. This should be done
using the PMconsole program. See the section on Global Configuration in
Chapter 3 for instructions on editing the global configuration.
[] Routing should be set to "Broadcast".
[] The broadcast address should be checked against the one being used by
other gateways on the local ethernet.
[] Slip should be "Enabled".
Port Configuration
Each Serial port which will has a modem attached, and will be used for Dialnet
connections should be configured. See the section on Setting the Serial
Port Configuration in Chapter 3 for instructions on editing the serial ports.
[] The serial port should be set to "Extended" Mode.
O The Port Type should be set to "Slip". The Slip Service should
be set to "Hardwired".
[] The destination, netmask, and routing should be set to match the remote
location.
D The Baud Rates, Modem Control, and Flow Control should be set to match
the modem.
Testing
To test a new connection:
[] Monitor the serial port, and the network statistics window using PMconsole
to verify that the connection is active. The use of these screens is described
in Monitoring the PortMaster in Chapter 3.
[] Verify that routing tables are properly configured. (ie. static routes
or dynamic routing (RIP). If using static routing, static route entries
will need to be entered into the Routes Table. See the section Managing
the Routes Table in Chapter 3 for more information.
[] Verify that the PortMaster is accessible to the remote computers through
the network (ie, "ping" the PortMaN
Verify that computers at each site are accessable]e (ie. use Rlogin, ping,
or telnet),
On To Administration