The LRS connects to remote nodes or networks using serial network links, which allow network traffic to flow through ordinary modems. This chapter discusses initiation, maintenance, and disconnection of these remote connections.

This chapter is intended to get users started remote networking. After completing this chapter, you should be able to configure the LRS to support the following:

Incoming remote node
Incoming character mode, PPP mode, and SLIP mode in a secure
manner
Basic outgoing LAN to LAN using PPP

The functionality described in this chapter may not meet all of your performance needs; in addition, it will not ensure complete network security. If your network requires more complex configuration, or you are not using modems, refer to Chapter 4 - Additional Remote Networking for additional configuration instructions.

3.2 Connection Types

The LRS enables two types of remote networking connections: LAN to LAN and remote node.

In LAN to LAN connections, the LRS provides a link between two networks. The LRS will communicate with a remote router, which may be another remote access server, a UNIX machine capable of PPP routing, or another LRS. The LRS may be connected to the remote router with temporary "dial on demand" connections such as ordinary dialup modems. The LRS may also be permanently connected to the remote router with leased lines, a statistical multiplexor, or a direct serial connection.

The LRS offers incoming and outgoing LAN to LAN connections. It can initiate outgoing LAN to LAN connections, or receive incoming LAN to LAN connections from remote locations.

LAN to LAN connections are often used to connect two locations that don't always need to be connected. For example, a small remote office with only a few nodes and a central office might need to be connected occasionally, however, the amount of traffic wouldn't warrant using a leased line for the connection. Using an LRS and dialup modems, the connection could come up and down when required, simulating a permanent connection between the two locations.

A remote node connection enables a single remote node (such as a PC) to use a network's services. For example, a laptop user on a business trip may wish to access files from a network's file server. Using a modem, the laptop could dial the LRS, form a connection, and download the files as if the laptop were directly connected to that network.

The LRS cannot initiate connections to remote nodes. Remote nodes must call the LRS when they wish to communicate with the network.

3.3 Managing Connections With Sites

A site represents a remote physical location, for example, a remote router or a remote node. Sites are referenced by a name, such as seattle. The site's name should indicate the physical location of the remote device, a group of remote node users, or a particular remote node user.

Using sites for connections enables each connection to have different characteristics; connections aren't limited solely to the characteristics of the port used.

Sites serve four purposes:

To configure the LRS and the remote router appropriately for a connection

: For example, particular LRS ports may be assigned for use with the connection.

To enforce specific network requirements

: For example, compression may be required for all connections.

To manage a connection once it is in place

: For example, the amount of bandwidth used for a connection may be controlled.

To enable a system administrator to monitor a single connection

: For example, a system administrator may wish to restrict remote node users to a particular range of IP addresses.

Every incoming and outgoing remote networking connection (LAN to LAN and remote node) has a site associated with it. To create and edit sites, see Setting Up Sites .

3.3.1 Incoming Connections (Remote Node or LAN to LAN)

Incoming connections can use either custom sites or share the default site's information by using temporary sites.

Custom sites are used when a specific configuration is required for the incoming router or remote node. Custom sites allow the most flexibility in the control and configuration of incoming connections. These sites should be named for the location or user that is calling the LRS.

Configuring a site for each caller can be time-consuming, and it consumes system resources. When the LRS must support a large number of incoming connections, using custom sites for each caller can require a great deal of time. If a group of incoming connections can use the same configuration, they can be allocated temporary sites used only for that session.

Each temporary site takes its configuration from the LRS default site. The default site may be customized in the same manner as custom (named) sites, this customized configuration can then be shared with many remote routers and remote nodes.

The default site configuration is listed in Table 3-1 .

When an incoming caller is allocated a temporary site, the name of the site is based on the port receiving the call. For example, an incoming call to port 3 may be allocated a temporary site named Port3.

3.3.2 Outgoing LAN to LAN Connections

A site must be configured for each outgoing LAN to LAN connection. This site controls when and how the LRS will call the remote location, what protocols to use, and when to terminate the connection.

Outgoing sites are typically named for the remote router that the LRS will call; for example, if a site is used for outgoing connections to a remote router in Dallas, the site used for the connection might be named dallas. This site could also be used for incoming calls; if the router in Dallas needed to call our LRS, it could use dallas to make the connection.

3.3.3 Setting Up Sites

The Define Site commands are used to create new sites and edit existing sites. The Show/Monitor/List Sites commands are used to get information about existing sites.

As these commands require privileged access, each example in this section denotes privileged status with the >> prompt. For information on obtaining privileged access, see Set Privileged/Noprivileged .

3.3.3.1 Creating a New Site

To create a new site, assign a name using the following command:

Figure 3-1: Creating New Site

Local>> DEFINE SITE IRVINE
When a site is defined, it uses a "factory default" configuration (see Default Site Configuration below). The site's settings may then be modified; see Editing Sites for instructions.

3.3.3.2 Displaying Existing Sites

To display currently active sites, use the Show Site command. To display all defined sites, use the List Site command.

The List Site command is used in Figure 3-2 because site irvine isn't currently running.

To display specific information about sites, the following parameters may be used in conjunction with Show Site and List Site: IP, IPX, Ports, Counters, and Status. For example, to display the IP configuration of site irvine, use the following command:

Figure 3-2: Displaying a Site's IP Configuration

Local>> LIST SITE IRVINE IP

3.3.3.3 Default Site Configuration

The default site configuration is used for all temporary sites. To display this configuration, use the following command:

Figure 3-3: Displaying Default Site

Local>> LIST SITE DEFAULT
The following table lists the default site configuration.

Table 3-1: Default Site Configuration

Characteristic Configuration in
Default Site
CHAP authentication on outgoing calls Disabled
PAP authentication on outgoing calls Disabled
Remote password None configured
Local password None configured
Username None configured
Chat script entries None
IP/IPX compression Enabled
IP/IPX packet forwarding Enabled
Maximum idle time 10:00 (10 minutes)
Remote host's IP configuration Undefined
IP compression slots 16
IPX compression slots 16
IPX keepalive spoofing Enabled
Maximum packet size (MTU): PPP 1522
Ports defined None
PPP Enabled
SLIP Disabled
Telephone number of remote site None defined
Outgoing packet filter None defined
Incoming packet filter None defined
Idle time filter None defined
Startup filter None defined
Maximum packet size (MTU): SLIP 1500
Time Filter None defined

Characteristic	Configuration in Default Site
CHAP authentication on outgoing calls	Disabled
PAP authentication on outgoing calls	Disabled
Remote password	None configured
Local password	None configured
Username	None configured
Chat script entries	None
IP/IPX compression	Enabled
IP/IPX packet forwarding	Enabled
Maximum idle time	10:00 (10 minutes)
Remote host's IP configuration	Undefined
IP compression slots	16
IPX compression slots	16
IPX keepalive spoofing	Enabled
Maximum packet size (MTU): PPP	1522
Ports defined	None
PPP	Enabled
SLIP	Disabled
Telephone number of remote site	None defined
Outgoing packet filter	None defined
Incoming packet filter	None defined
Idle time filter	None defined
Startup filter	None defined
Maximum packet size (MTU): SLIP	1500
Time Filter	None defined

3.3.4 Editing Sites

All site characteristics can be edited with the Define Site commands. For example, a site's authentication can be edited with the command below:

Figure 3-4: Editing Site Characteristic

Local>> DEFINE SITE irvine AUTHENTICATION PAP DISABLED
Currently active sites cannot be edited. Changes will not take effect until the site is logged out.

3.3.5 Deleting Sites

To delete a site, use the Purge Site command.

Figure 3-5: Deleting a Site

Local>> PURGE SITE irvine
When the Purge command is used with the default site, the site's default configuration will be restored. Any editing changes you've made to the default site will be removed.

Figure 3-6: Restoring Default Site Configuration

Local>> PURGE SITE DEFAULT

3.4 IP and IPX Addressing

3.4.1 IP Address Assignment

By default, all sites will use "unnumbered" interfaces for IP. The IP address of the LRS's Ethernet will be used as the LRS's IP address on all serial ports. This reduces the amount of required configuration, in addition, it eliminates the need to allocate a separate IP network for each port.

When the LRS receives an incoming connection request (remote node or LAN to LAN), an IP address is negotiated for the caller. The address agreed upon depends on the caller's requirements; some don't have a specific address requirement, while others must use the same IP address each time they log into the LRS.

PPP negotiation is covered in Chapter 7 - PPP.

For a complete discussion of IP address assignment (including configuration instructions), see Remote Networking IP Address Assignment .

3.4.2 IPX Address Assignment

Every IPX network (including all serial links to remote sites) must be assigned a unique IPX network number. When the LRS is initially configured, a range of IPX network numbers (called a netrange) must be defined. The LRS will use the netrange to allocate a network number to each port.

To specify the base number of the range, use the Set/Define IPX Netrange command. Each serial port will be assigned an IPX network number equalling the sum of the base number and its port number.

Figure 3-7: Defining IPX Netrange

Local>> DEFINE IPX NETRANGE 0x100
On the LRS16, the netrange shown in Figure 3-7 is 0x101 to 0x110.

3.5 IP and IPX Routing

The following sections discuss IP and IPX routing issues as they pertain to remote networking. For a complete discussion of IP Routing, refer to Chapter 5 - IP. For coverage of IPX routing, see Chapter 6 - IPX.

When a packet is received or generated that is destined for a remote network, the LRS will check its routing table to determine the most efficient route to the destination. If the LRS does not have a route to a remote network, it cannot send the packet to the destination. The entries in the routing table are one of three types:

Local routes: Shows that a network is directly attached. This route is automatically determined from the LRS's IP address and network mask and is never deleted.
Static routes: Manually entered in the routing table by a system administrator. These routes are used when dynamic routes cannot be.
Dynamic routes: Learned through the receipt of RIP (Routing Information Protocol) packets.

Each routing entry can point to another router on the Ethernet or to a site configured for LAN to LAN connections.

3.5.1 Outgoing LAN to LAN

Generally, the LRS has static routes configured for each remote LAN that it will connect to. These routes point to sites that are configured for outgoing LAN to LAN connections. The first time that the LRS needs to send a packet destined for a network on a remote LAN, the site will be activated and the LRS will attempt to call the remote router. Once the connection has been formed, subsequent packets for the remote LAN will be forwarded over that link.

While the LRS is connected to the remote router, it may learn additional dynamic routes from that remote router. Once these additional routes are entered into the routing table, packets may be routed to these new networks as well. Once the connection is dropped, the LRS can be configured to maintain these routes. Subsequent traffic to these dynamically learned networks or to the pre-existing static route networks will cause the site to form a new connection.

If the LRS is a stub router (or you're using the LRS to connect to the Internet), default routes can be used to reduce configuration time. A stub router connects a LAN without any other routers to a larger LAN. For example, in a remote office with no other outside connections, an LRS that connects to exactly one other (larger) location is a stub router. All traffic generated on the remote office's LAN that is destined for the remote location must pass through the LRS. A default route pointing to the larger site may be entered on the LRS.

Default routes should be used with caution. See Chapter 5 - IP or Chapter 6 - IPX for complete details.

3.5.2 Incoming LAN to LAN

If RIP is being used, no static routing entries need to be configured on the LRS. Routes to networks on the remote LAN will be learned automatically.

RIP is enabled by default.

If RIP is not being used, the LRS must have a specific site configured for this incoming connection. The remote router must utilize this site when it connects to the LRS. The site may be started in one of two ways: through the authentication sequence (which requires that authentication be appropriately configured), or with the Set PPP <sitename> command. Static routes pointing to the site must be configured for each of the incoming caller's IP or IPX networks.

To configure authentication, see Setting up Incoming LAN to LAN and Remote Node or Chapter 11 - Security.

3.5.3 Remote Node

The LRS automatically generates routes for remote nodes when the node connects. These routes are deleted when the connection is terminated.

If the remote node receives a dynamic address from the LRS's IP address pool, a host route is entered for that address. If proxy ARPing is enabled (see Proxy ARP ), the LRS will proxy ARP for the address.

See Host Routes for more information.

If a remote node uses an IP address that is not on the Ethernet's IP network, then the LRS will enter a network route for that node. For example, if the LRS's Ethernet IP address is 192.0.1.4, and a node selects the address 192.0.2.6, the LRS will enter a route to 192.0.2.0 in its routing table.

IPX remote nodes are always on the IPX network assigned to the port that the call was received on. The LRS will add a route to that port's network number.

Remote nodes do not have to make routing decisions, as they can only send network packets to the LRS. Therefore, most remote nodes do not need to receive RIP packets. Sites that only support remote nodes may turn off RIP to reduce traffic on the connection.

To disable RIP, see Define Site IP or Define Site IPX .

3.6 PPP and SLIP

The LRS uses asynchronous serial lines to connect remote locations. A protocol is then run on this serial connection to allow network packets to be sent.

The LRS supports the use of PPP and SLIP to send network packets.

PPP: PPP is the Point to Point protocol. Its use is recommended wherever possible. PPP enables devices to simultaneously transport IP and IPX packets, negotiate certain options, authenticate users, and use checksums with virtually no performance loss.
SLIP: SLIP is the Serial Line Internet Protocol. It is supported primarily for backwards compatibility with equipment that doesn't support PPP. SLIP can only transport IP packets. It does not support negotiation of IP addresses or other options, nor does it provide any diagnostic facilities.

For a complete description of PPP, see Chapter 7 - PPP.

3.7 Incoming LAN to LAN and Remote Node

When an incoming LAN to LAN or remote node connection is initiated, there are a number of ways that PPP or SLIP may be started:

The caller may be presented with a Local> prompt (the port will be in character mode), requiring them to enter commands in order to run PPP or SLIP.

For a description of the port modes, see Port Modes .

The port may detect when a PPP or SLIP packet is received and automatically run the appropriate protocol.
The port may be dedicated to PPP or SLIP; the protocol will automatically run when any character is received.

A port may be configured to offer a combination of these methods; giving the incoming remote node or router flexibility in how the connection is started .

To configure the LRS for incoming LAN to LAN and remote node connections, see Setting up Incoming LAN to LAN and Remote Node .

3.7.1 Starting PPP or SLIP from the Local> Prompt

The Set PPP and Set SLIP commands may be entered from the Local> prompt. The remote router or node must pass through the authentication procedures, if enabled, on the port in character mode. The remote device must support chat scripts or must rely on a user to enter the required information and type Set PPP or Set SLIP at the Local> prompt.

For a complete description of authentication, refer to Chapter 11 - Security. For information on chat scripts, see Chat Scripts .

If no arguments are given to Set PPP or Set SLIP, a temporary copy of the default site will be started. If a custom site is to be started, it can be specified as an argument: Set PPP <sitename>.

Users can be prompted for the site's local password to prevent users from starting inappropriate sites.

To use the Set PPP/Set SLIP commands, PPP and/or SLIP must enabled on the port used for the connection. For more information, see Define Port PPP or Define Port SLIP .

3.7.2 Starting PPP or SLIP Using Automatic Protocol Detection

Automatic Protocol Detection allows the LRS to determine what type of connection the remote device is attempting to establish. By detecting which protocol is to be run on each connection, a port can support character mode (Local> prompt) connections, PPP connections, and SLIP connections without reconfiguration. One modem pool can support all incoming connections; there is no need to dedicate ports to remote networking.

To configure autodetection, see Chapter 8 - Ports.

By default, the LRS detects character mode by looking for the return character.

If PPPdetect is enabled on the port, and a PPP packet is detected, PPP will be started with a temporary copy of the default site.

A custom site can also be run by enabling PPP authentication on the port. If the remote device sends a valid username and password and the username matches a site name, that site will start running on the port. All further configuration of the connection will be from this new site.

If PPP authentication is not enabled on this port, there is a security risk. Unauthorized users may gain access to your network. Use dedicated PPP mode with PPP authentication (CHAP or PAP) wherever possible. If PPP authentication is not possible, use port authentication and the Set PPP command to authenticate incoming calls.

To configure PPP authentication, see Chapter 11 - Security.

If SLIPdetect is enabled on the port, and a SLIP packet is detected, SLIP will be started. SLIP does not support authentication. Incoming connections to a port in dedicated SLIP mode cannot be authenticated. This is a security risk in most situations. Unauthorized users may gain access to your network. Use this mode with caution.

Custom sites cannot be run when using dedicated SLIP as there is no method to switch sites once the temporary site is running. Start SLIP with the Set SLIP command to allow custom sites and to authenticate incoming calls.

3.7.3 Starting PPP or SLIP on a Dedicated Port

A port may be dedicated to PPP or SLIP mode. Whenever the port receives a character, it starts up a temporary copy of the default site using the appropriate link layer. The port cannot be used for character mode connections and the Local> prompt cannot be reached.

To dedicate a port, see Preferred/Dedicated Services and Protocols .

Once PPP or SLIP is running, the behavior of a dedicated port is the same as a port with automatic protocol detection enabled. See Starting PPP or SLIP Using Automatic Protocol Detection for information about security issues.

For more information on dedicated ports, see Preferred/Dedicated Services and Protocols .

3.7.4 Incoming Connection Sequence

The following steps detail the events that occur when the LRS receives an incoming call.

3.7.4.1 Port Automatically Runs PPP or SLIP

If the port receiving the call is using automatic protocol detection, or is dedicated to SLIP or PPP, the following sequence of events will take place:

1. If automatic protocol detection (for PPP, SLIP, or both) is enabled, the link layer will start up automatically when a PPP or SLIP character is received from the incoming call. If the port is dedicated, the link layer will start upon the receipt of any character.

2. The caller will be attached to a temporary site. The name of this site will be based on the port number used. For example, an incoming call to port number 6 will generate a temporary site named Port6.

A. If using SLIP, callers will continue to use the temporary site for the remainder of the connection.

B. If using PPP, the following steps will occur:

1. If the LRS port receiving the call has been configured to authenticate remote hosts using CHAP or PAP, CHAP/PAP will request a username and password from the remote host. If the remote host has been configured to send a username and password, it will send the pair to the LRS.

2. The username and password will be compared to existing site names. One of the following will occur:

a. If the username matches the name of a site, the site will be checked to see if it has a local password. If it does, this will be compared to the password entered by the caller. If the passwords match, the user will begin using the custom site; the temporary site will stop running.

b. If the site isn't configured with a password, or the password entered by the caller doesn't match the site password, the username/password pair will be compared to any authentication databases. One of two outcomes is possible:

If a match is found, the connection will be successfully authenticated, and the caller will continue using the temporary site for the remainder of the connection.

If a match is not found, the connection attempt will fail.

3.7.4.2 Port Doesn't Automatically Run PPP or SLIP

If an incoming call is received on an LRS port that's not configured to automatically run PPP or SLIP, the following login sequence will occur:

1. The caller sends a carriage return.

2. If the port is configured to prompt for a login password, the caller will need to enter the correct login password to continue. Once this is entered, the Local> prompt will be displayed.

3. If the port is configured to prompt for a username, the caller will need to enter a username.

4. If the port is configured for authentication, the caller will need to enter a valid password for the username.

5. To start the link layer, the user will need to enter commands to start PPP or SLIP. One of two scenarios will occur:

A. If the caller specifies a particular site to be started when PPP or SLIP is started, the user will be attached to this site. If the site has been configured to prompt for its local password, the user will have to enter the site's local password. At this point, the caller will be unable to run another site.

B. If a site isn't specified, the user will be attached to a temporary site. The name of this site will be based on the port number used. For example, an incoming call to port number 6 will generate a temporary site named Port6. This site will be used for the remainder of the call.

Incoming LAN to LAN connections will need to enter commands via a chat script. See Chat Scripts .

3.7.5 Setting up Incoming LAN to LAN and Remote Node

To configure the LRS for incoming connections, complete the steps in the following sections.

3.7.5.1 Configure Ports

Port configuration for incoming connections involves a number of factors: whether PPP or SLIP will be used, whether the ports will be dedicated to PPP or SLIP, whether autodetection of PPP or SLIP will be used, and if a modem is attached to any of the ports, how it will be configured.

To configure a port's use of PPP or SLIP, see Chapter 8 - Ports. To configure modems, see Chapter 9 - Modems.

3.7.5.2 Create Site(s)

If users will be starting up custom sites (by entering a username that matches an existing site name), those sites must be created. See Creating a New Site for instructions.

3.7.5.3 Configure Authentication

3.7.5.3.1 Login Password

In order to use a login password, a port must support use of the character mode. When a port is configured to automatically run PPP or SLIP, the opportunity to enter the login password will be bypassed. See Chapter 8 - Ports to configure a port's use of modes.

Determine a login password. Set the password using the Set/Define Server Login Password command.

Figure 3-8: Defining Login Password

Local>> DEFINE SERVER LOGIN PASSWORD badger
Enable the use of the login password on the appropriate port(s) using the following command:

Figure 3-9: Enabling Login Password

Local>> DEFINE PORT 3 PASSWORD ENABLED

LRS passwords are case-independent, even when enclosed in quotes.

By default, incoming Telnet and Rlogin connections are not required to enter the login password. To require the login password, use the Set/Define Server Incoming command.

3.7.5.3.2 Username/Password Authentication

Enable authentication on the appropriate ports.

Figure 3-10: Enabling Authentication

Local>> DEFINE PORT 2 AUTHENTICATE ENABLED
If authentication should be performed before PPP or SLIP are running (while the port is still in character mode), ensure that autodetection of PPP and SLIP is disabled [Figure 3-11]. Keep in mind that PPPdetect and SLIPdetect will only need to be disabled on ports that have PPP and/or SLIP enabled.

Figure 3-11: Disabling Autodetection of PPP and SLIP

Local>> DEFINE PORT 2 PPPDETECT DISABLED
Local>> DEFINE PORT 2 SLIPDETECT DISABLED
In order for SLIP users to perform authentication, SLIPdetect must be disabled. SLIP users will only be able to authenticate incoming connections while the port is in character mode; once the port is running SLIP (for example, if the port is dedicated to SLIP using the Set/Define Port SLIP Dedicated command) authentication cannot be performed.

If the port is configured to automatically run PPP, and you'd like to use CHAP or PAP to obtain a username and password from the incoming caller, enable remote CHAP and/or PAP authentication on the desired port.

Figure 3-12: Enabling CHAP Authentication

Local>> DEFINE PORT 2 PPP CHAP REMOTE
Local>> DEFINE PORT 2 PPP PAP REMOTE

CHAP and PAP may both be enabled on the same port.

If incoming connections will be entering usernames to start a custom site, ensure that the site has a local password. Callers will be required to enter this password in order to start the site.

Figure 3-13: Configuring Site's Local Password

Local>> DEFINE SITE irvine AUTHENTICATION LOCAL "gorilla"
Configure any databases that will be used for authentication and add the appropriate usernames and passwords. See Chapter 11 - Security for configuration instructions.

3.8 Outgoing LAN to LAN Connections

When the LRS receives a packet, it will consult its routing table to determine the best route to the packet's destination. If the specified route points to a site, a connection to the site may be initiated. The connection will be subject to any restrictions defined for the site, such as a startup filter or time of day restrictions.

While a connection to the remote router is initiated, a limited number of packets will be buffered until the connection is formed. When the connection is successful, the packets will be sent.

To restrict outgoing connections, see Chapter 11 - Security.

3.8.1 Ports

Each site must specify which LRS port(s) may be used for outgoing connections. More than one port may be specified; for example, site dallas might specify that port 2 or port 3 could be used for outgoing connections.

When the LRS attempts to make a connection to a site, it will attempt to use one of the specified ports. If the port is busy (in use with another connection), it will attempt to make a connection using another specified port. If all ports are busy, the LRS will time out the site for a few minutes and then try again. This connection timeout between call attempts is user configurable. See Define Site Time Failure.

More than one site may specify a particular port. For example, site dallas and site seattle might specify that port 3 may be used for connections. If site dallas is using port 3 at a certain time and site seattle attempts to use the port, seattle will attempt a connection using another specified port. If no other port is specified, seattle will wait to use port 3 until it becomes available.

To learn how incoming calls use ports and sites, see Incoming LAN to LAN and Remote Node .

3.8.2 Telephone Numbers

Each site may specify one port-independent telephone number, and one or more port-specific telephone numbers. A port-independent telephone number is typically used if all ports are configured to call the same number, for example, if the ports are calling a telephone hunt group. Port-independent telephone numbers should be used whenever possible; this frees a site to dial the remote site's number from any of the ports the site is associated with.

Port-specific telephone numbers are used when a particular LRS port should call a specific number at the remote site. These numbers will override a port-independent telephone number. For example, in order to get the most efficient use out of connected modems, a site might specify that when port 2 (connected to a high speed modem) is used, another high speed modem should be dialed. When port 3 (connected to a slow speed modem) is used, the LRS should dial another slow speed modem.

If a site does not have a telephone number defined, the LRS assumes either that there's a direct connection between the LRS and the remote host, or that a chat script (see Chapter 4 - Additional Remote Networking) will be used to communicate with the remote host.

3.8.3 Authentication

The remote site may require that the LRS authenticate itself by sending a username and password. The username that the LRS sends is (by default) the site name. To send a different username, use the Define Site Authentication Username command.

The password sent is a site-specific password called the remote password. The remote password is used only for outgoing connections, and must be sent via PPP. See Configure Authentication for configuration instructions.

SLIP does not support authentication. To perform authentication, SLIP users must use chat scripts. See Chat Scripts .

3.8.4 Setting up Outgoing LAN to LAN Connections

To configure the LRS for outgoing connections, complete the steps in the following sections.

3.8.4.1 Configure Ports

All ports that will support outgoing connections must be configured for dynamic connections. Use the following command:

Figure 3-14: Permitting Outgoing Connections

Local>> DEFINE PORT 2 ACCESS DYNAMIC

For more information on port configuration, see Chapter 8 - Ports.

3.8.4.2 Configure Modems

Enable modem operation on the port(s) used for outgoing calls. Then assign a modem profile to the port using the Define Port Modem Type command.

Figure 3-15: Enabling Modem Operation

Local>> DEFINE PORT 2 MODEM ENABLED
Local>> DEFINE PORT 2 MODEM TYPE 5

A modem profile automatically sets up a port for a specific type of modem. See Define Port Modem Type .

Modem profiles and complete modem configuration instructions are discussed in Chapter 9 - Modems.

3.8.4.3 Create a Site

Every outgoing connection must use a site. To create a site, see Creating a New Site . Each site is initially created with a default set of configurations. To display the current configuration, use the List Site command:

Figure 3-16: Listing a Site's Configuration

Local>> LIST SITE irvine PORTS
List Site can be used with a number of parameters, which display different aspects of a site's configuration. For example, the List Site Ports will display all ports associated with the site.

3.8.4.4 Select Port(s) to Use for Dialing Out

Once a site is created, the port(s) that it will use to dial the remote location must be defined. Each site must be associated with at least one port. Use the following command:

Figure 3-17: Associating a Site With a Port

Local>> DEFINE SITE irvine PORT 2

3.8.4.5 Assign A Telephone Number to the Port or Site

If the site will be used with modems, at least one telephone number must be specified in order for the site to dial a remote host. The number may be assigned specifically for use with a particular port, or for use with any port. To assign a port-specific telephone number, use the Define Site Port Telephone command:

Figure 3-18: Assigning a Port Telephone Number

Local>> DEFINE SITE irvine PORT 2 TELEPHONE 547-9549
To assign a telephone number to the site that may be used with any port, use the Define Site Telephone command:

Figure 3-19: Assigning a Site Telephone Number

Local>> DEFINE SITE irvine TELEPHONE 867-5309
A port-specific telephone number will override a site telephone number. For example, site irvine may be configured to use the number 635-9202 on any port it's using, but configured to use the number 845-7000 when it's using port 3.

3.8.4.6 Configure Authentication

When an outgoing connection is attempted, the remote router may or may not require the LRS to authenticate itself. One of the following scenarios will generally apply:

The remote router uses CHAP or PAP to prompt the LRS to authenticate itself
This scenario is the most common; the configuration instructions in this section assume that CHAP or PAP will be used.
The remote router requires a login password
In this case, the LRS will need to use a chat script to communicate this password to the remote router. See Chapter 4 - Additional Remote Networking for instructions.
The remote router does not require authentication
The instructions in this section will not be necessary. Continue to Configure Routing .

Before configuring authentication, ensure that you have the username and password required to log into the remote router. In addition, determine whether the remote router will use PAP or CHAP to transmit the username and password.

Configure the username and remote password to be transmitted.

Figure 3-20: Defining Local Username and Password

Local>> DEFINE SITE irvine AUTHENTICATION USERNAME "doc_server"
Local>> DEFINE SITE irvine AUTHENTICATION REMOTE "giraffe"
If CHAP will be used, enable CHAP on the site. To use PAP to transmit the username and password, enable PAP on the site.

Figure 3-21: Enabling CHAP/PAP Authentication

Local>> DEFINE SITE irvine AUTHENTICATION CHAP ENABLED
Local>> DEFINE SITE irvine AUTHENTICATION PAP ENABLED

3.8.4.7 Configure Routing

Static routes to the sites must be entered in the IP and IPX routing tables.

To configure IP Routing, see Chapter 5 - IP. To configure IPX routing, see Chapter 6 - IPX.

3.9 Monitoring Networking Activity

To monitor current remote networking activity, use the Show Site or Monitor Site command. Show Site enables you to display the activity associated with a particular site, including the number of packets received and transferred, idle time, current state of the site's ports, and configuration of its associated protocols (for example, IP). Monitor Site will update and redisplay this information at three-second intervals.

Table 3-2: Show/Monitor Site Commands

Command Description
Show/Monitor Site s Lists currently running sites.
Show/Monitor Site <sitename> Displays the site's configuration
Show/Monitor Site <sitename> Counters Displays the site's current performance
Show/Monitor Site <sitename> Status Shows all sites that have attempted or completed connections.
Show/Monitor Site <sitename> Status Shows cumulative statistics for this site. Statistics are reset upon boot.
During active connections, Show/Monitor Site commands will display the current state of the site or of its assigned ports. The state of the port or site depends on the activity taking place. For example, a port may be in an idle state, then transition to an online state when it begins transferring packets.

Command	Description
Show/Monitor Site s	Lists currently running sites.
Show/Monitor Site <sitename>	Displays the site's configuration
Show/Monitor Site <sitename> Counters	Displays the site's current performance
Show/Monitor Site <sitename> Status	Shows all sites that have attempted or completed connections.
Show/Monitor Site <sitename> Status	Shows cumulative statistics for this site. Statistics are reset upon boot.

Table 3-3: Site States

Site State Activity During State
Idle The site is idle.
Startup A user, PPP, or SLIP requested that the site start running.
Waiting The site is waiting for a port to connect.
Connect The site is connected and passing packet traffic.
Logout The site was instructed to shut down.
Closing The site is shutting down PPP or SLIP.
Freeing The site is removing itself from memory.
NVR A List Site command was used to display site information. The site's configuration is displayed, not its current activity.

Site State	Activity During State
Idle	The site is idle.
Startup	A user, PPP, or SLIP requested that the site start running.
Waiting	The site is waiting for a port to connect.
Connect	The site is connected and passing packet traffic.
Logout	The site was instructed to shut down.
Closing	The site is shutting down PPP or SLIP.
Freeing	The site is removing itself from memory.
NVR	A List Site command was used to display site information. The site's configuration is displayed, not its current activity.

Table 3-4: State of Ports Assigned to a Site

Port State Activity During State
Idle The site is not currently using this port. The port may be in use by other sites.
Dial The remote modem is being dialed.
Chat The chat script defined in the site is being executed. See Chapter 4 - Additional Remote Networking for a definition of chat scripts.
Link PPP is being negotiated with the remote router or remote node. (This state does not apply to SLIP users).
Ready PPP negotiation has been completed. (This state does not apply to SLIP users).
Online Traffic is being forwarded to the remote site.

Port State	Activity During State
Idle	The site is not currently using this port. The port may be in use by other sites.
Dial	The remote modem is being dialed.
Chat	The chat script defined in the site is being executed. See Chapter 4 - Additional Remote Networking for a definition of chat scripts.
Link	PPP is being negotiated with the remote router or remote node. (This state does not apply to SLIP users).
Ready	PPP negotiation has been completed. (This state does not apply to SLIP users).
Online	Traffic is being forwarded to the remote site.

3.10 Examples

3.10.1 LAN to LAN - Calling one Direction Only

An LRS in a remote office in Dallas must call an LRS at the company headquarters in Seattle. This LAN to LAN connection must meet the following criteria:

IP users in a remote office in Dallas must connect to IP network 192.0.1.0, which is located at the company headquarters in Seattle.
Novell users in Dallas must connect to the Novell file server called MServ in Seattle. This file server has the internal network number 1234abcd.
The NetWare network in Seattle uses frame type 802.3 and network number 56ce.
The NetWare network in Dallas uses frame type 802.2 and network number ab12.
There are no NetWare network numbers in the range 0x131-0x133.
The LRS in Seattle never calls Dallas.
Both IP and IPX traffic must be transferred.
The LRS in Seattle must support character mode users as well as the LRS in Dallas.
After 60 seconds of idle time, the connection between Dallas and Seattle should be timed out.

3.10.1.1 LRS in Dallas

This LRS must be configured for outgoing LAN to LAN connections.

Figure 3-22: Dallas LRS Configuration

Local>> DEFINE PORT 2 ACCESS DYNAMIC
Local>> DEFINE PORT 2 MODEM ENABLED
Local>> LIST MODEM
Local>> DEFINE PORT 2 MODEM TYPE 1
Local>> DEFINE PORT 2 MODEM SPEAKER DISABLED
Local>> DEFINE PORT 2 AUTHENTICATE ENABLED
Local>>
Local>> DEFINE SITE SEATTLE AUTHENTICATION USERNAME "dallas"
Local>> DEFINE SITE SEATTLE AUTHENTICATION REMOTE "xyz"
Local>> DEFINE SITE SEATTLE AUTHENTICATION CHAP ENABLED
Local>> DEFINE SITE SEATTLE IDLE 60
Local>> DEFINE SITE SEATTLE PORT 2
Local>> DEFINE SITE SEATTLE TELEPHONE 2065551234
Local>>
Local>> DEFINE IP ROUTE 192.0.1.0 SITE SEATTLE 2
Local>>
Local>> DEFINE IPX FRAME 802.2 NETWORK ab12
Local>> DEFINE IPX FRAME 802.2 ENABLED
Local>> DEFINE IPX NETRANGE 130
Local>> DEFINE IPX ROUTING ENABLED
Local>> DEFINE IPX SERVICE MServ 4 1234abcd 00-00-00-00-00-01 451 2
Local>> DEFINE IPX ROUTE 1234abcd SITE SEATTLE 2 10
Local>>
Local>> INITIALIZE SERVER DELAY 0
The Initialize Delay 0 command will reboot the LRS; when the unit has rebooted, changes made with the Define commands will be in effect.

3.10.1.2 LRS in Seattle

Figure 3-23: Seattle LRS Configuration

Local>> DEFINE PORT 2 MODEM ENABLED
Local>> LIST MODEM
Local>> DEFINE PORT 2 MODEM TYPE 1
Local>> DEFINE PORT 2 MODEM SPEAKER DISABLED
Local>> DEFINE PORT 2 AUTHENTICATE ENABLED
Local>> DEFINE PORT 2 PPPDETECT ENABLED
Local>> DEFINE PORT 2 PPP CHAP REMOTE
Local>> DEFINE PORT 2 AUTHENTICATE ENABLED
Local>> LOGOUT PORT 2
Local>>
Local>> DEFINE SITE dallas AUTHENTICATION LOCAL "xyz"
Local>> DEFINE IPX FRAME 802.3 ENABLED
Local>> DEFINE IPX FRAME 802.3 NETWORK 56ce
Local>> DEFINE IPX NETRANGE 140
Local>> DEFINE IPX ROUTING ENABLED
Local>>
Local>> INITIALIZE SERVER DELAY 0

3.10.2 LAN to LAN - Bidirectional (Symmetric) Calling

An LRS in a remote office in Dallas must be able to call an LRS at the company headquarters in Seattle. This LAN to LAN connection must meet the following criteria:

The LRS in Seattle must also be able to call Dallas.
Both IP and IPX traffic must be transferred.
IP users in Dallas must connect to IP network 192.0.1.0, which is located in Seattle.
IP users in Seattle must connect to IP network 192.0.2.0, which is located in Dallas.
Novell users in Dallas must connect to the Novell file server called MServ in Seattle. This file server has the internal network number 1234abcd. There are no file servers located in Dallas.
The NetWare network in Seattle uses frame type 802.3 and network number 56ce. The NetWare network in Dallas uses frame type 802.2 and network number ab12.
There are no NetWare network numbers in the range 0x141-0x143.
Both remote access servers are to be dedicated to this purpose. No other applications are to be supported.
After 60 seconds of idle time, the connection between Dallas and Seattle should be timed out.
The LRS in Seattle expects the username dallas and the password xyz.
The LRS in Dallas expects the username seattle and the password abc.
There are no NetWare network numbers in the range 0x131-0x133.

3.10.2.1 LRS in Dallas

This LRS must be configured for incoming and outgoing LAN to LAN connections:

Figure 3-24: Dallas LRS Configuration

Local>> DEFINE PORT 2 ACCESS DYNAMIC
Local>> DEFINE PORT 2 PPP DEDICATED
Local>> DEFINE PORT 2 MODEM ENABLED
Local>> LIST MODEM
Local>> DEFINE PORT 2 MODEM TYPE 1
Local>> DEFINE PORT 2 MODEM SPEAKER DISABLED
Local>> DEFINE PORT 2 AUTHENTICATE ENABLED
Local>>
Local>> DEFINE SITE SEATTLE AUTHENTICATION USERNAME "dallas"
Local>> DEFINE SITE SEATTLE AUTHENTICATION LOCAL "abc"
Local>> DEFINE SITE SEATTLE AUTHENTICATION REMOTE "xyz"
Local>> DEFINE SITE SEATTLE AUTHENTICATION CHAP
Local>> DEFINE SITE SEATTLE IDLE 60
Local>> DEFINE SITE SEATTLE PORT 2
Local>> DEFINE SITE SEATTLE TELEPHONE 2065551234
Local>>
Local>> DEFINE IP ROUTE 192.0.1.0 SITE SEATTLE 2
Local>>
Local>> DEFINE IPX FRAME 802.2 NETWORK ab12
Local>> DEFINE IPX FRAME 802.2 ENABLED
Local>> DEFINE IPX NETRANGE 130
Local>> DEFINE IPX ROUTING ENABLED
Local>> DEFINE IPX SERVICE MServ 4 1234abcd 00-00-00-00-00-01 451 2
Local>> DEFINE IPX ROUTE 1234abcd SITE SEATTLE 2 10
Local>>
Local>> INITIALIZE SERVER DELAY 0
The Initialize Delay 0 command will reboot the LRS; when the unit has rebooted, changes made with the Define commands will be in effect.

3.10.2.2 LRS in Seattle

The Seattle LRS will have different authentication, telephone, site and router information than the LRS in Dallas. In all other respects, it is configured identically to the Dallas LRS.

Figure 3-25: Seattle LRS Configuration

3.10.3 LAN to LAN Routing Without RIP

3.10.4 Remote Node

This example sets up ports 2 and 3 to support IP and IPX remote node users via PPP. All users will use temporary copies of the default site and may authenticate with CHAP, PAP, or chat scripts. Modems on port 2 and 3 will be automatically configured.

IP users will be forced to use either IP address 192.0.1.7 or 192.0.1.8. One IP user wwwserver, must have the same address (192.0.2.6) each time it logs in.

3.10.4.1 Configuring the Port

Figure 3-26: Configuring the Port

Local>> DEFINE PORT 2-3 PPPDETECT ENABLED
Local>> DEFINE PORT 2-3 PPP ENABLED
Local>> DEFINE PORT 2-3 PPP CHAP REMOTE
Local>> DEFINE PORT 2-3 PPP PAP REMOTE
Local>> DEFINE PORT 2-3 AUTHENTICATE ENABLED
Local>> DEFINE PORT 2-3 MODEM ENABLED
Local>> LIST MODEM
Local>> DEFINE PORT 2 MODEM TYPE 1
Local>> DEFINE PORT 3 MODEM TYPE 2

3.10.4.2 Configure IP to Allocate IP Addresses to Incoming Users

Figure 3-27: Configuring IP

Local>> DEFINE IP IPADDRESS 192.0.1.6
Local>> DEFINE IP ETHERNET POOL 192.0.1.7 192.0.1.8
Local>> DEFINE IP ETHERNET PROXY-ARP ENABLED

3.10.4.3 Configure IPX Network Range

Figure 3-28: Configuring IPX

Local>> DEFINE IPX NETRANGE 500

3.10.4.4 Configure Range of IP Addresses for Users of Default Site

Figure 3-29: Configuring Default Site

Local>> DEFINE SITE DEFAULT IP REMOTEADDRESS 192.0.1.7 192.0.1.8

3.10.4.5 Configure a Static IP Address Site

Figure 3-30: Configuring Static IP Address

Local>> DEFINE SITE wwwserver REMOTEIP 192.0.2.6
Local>> DEFINE SITE wwwserver IPX DISABLED
Local>> DEFINE SITE wwwserver AUTHENTICATION LOCAL "monkey"

3.11 Troubleshooting

The following table discusses some common problems that occur with remote networking configuration and proposes solutions for each.

Table 3-5: Common Remote Networking Problems

Problem Remedy
Outgoing LAN to LAN site does not dial the modem. Ensure that the site has ports and at least one telephone number assigned. In addition, ensure that Modem Control is enabled (Define Port Modem Control), and the modem profile is defined on the port.
Modem dials, but does not connect. Enable the modem's speaker using the Define Port Modem Speaker command.
Determine if the remote node is busy.
Ensure that the correct number is being called.
Check the Error Correction and Compression configuration.
Chat script doesn't complete. Enable chat script logging using the Set/Define Logging command.
Modem connects but connection drops. Ensure that authentication is defined correctly on the outgoing site.
Enable PPP and Site Logging using the Set/Define Logging command.
Ensure that the usernames/passwords being used match the expected usernames/passwords on the remote site.
Connection is established, but traffic does not flow. Determine if the modems are passing data by checking the send and receive lights on the LRS and the modem; the lights should be flashing.
Ensure that routes are configured correctly by using the Show/Monitor/List IPX Routes and Show/Monitor/List IP Routes commands.
Enable IP and IPX logging using the Set/Define Logging command.

Problem	Remedy
Outgoing LAN to LAN site does not dial the modem.	Ensure that the site has ports and at least one telephone number assigned. In addition, ensure that Modem Control is enabled (Define Port Modem Control), and the modem profile is defined on the port.
Modem dials, but does not connect.	Enable the modem's speaker using the Define Port Modem Speaker command.
	Determine if the remote node is busy.
	Ensure that the correct number is being called.
	Check the Error Correction and Compression configuration.
Chat script doesn't complete.	Enable chat script logging using the Set/Define Logging command.
Modem connects but connection drops.	Ensure that authentication is defined correctly on the outgoing site.
	Enable PPP and Site Logging using the Set/Define Logging command.
	Ensure that the usernames/passwords being used match the expected usernames/passwords on the remote site.
Connection is established, but traffic does not flow.	Determine if the modems are passing data by checking the send and receive lights on the LRS and the modem; the lights should be flashing.
	Ensure that routes are configured correctly by using the Show/Monitor/List IPX Routes and Show/Monitor/List IP Routes commands.
	Enable IP and IPX logging using the Set/Define Logging command.

3.12 Quick Reference

Managing Connections
To	Use This Command	Example(s)	What Example Does
Manage Connections Using a Custom Site	Define Site	DEFINE SITE dallas	Creates a custom site named "dallas". When a connection is made to a remote LRS in Dallas, "dallas" manages the connection, including when the link is brought up and down. See Managing Connections With Sites for more information.
Display a Site's Configuration (Custom Site or Default Site)	Show/Monitor/List Sites	LIST SITE default	Displays information about the default site, including whether PPP or SLIP is used, CHAP/PAP status, and any filter lists associated with the site. See Displaying Existing Sites for more information.
Edit a Custom or Default Site Configuration	Define Site <characteristic>	DEFINE SITE irvine AUTHENTICATION PAP DISABLED	Disables PAP authentication for site "irvine". See Editing Sites for more information.
Delete a Site	Purge Site	PURGE SITE irvine	Deletes site "irvine". See Deleting Sites for more information.
		PURGE SITE default	Restores the default site to its factory default configuration; any changes will be removed.
IP Address Assignment
To	Use This Command	Example(s)	What Example Does
Restrict Incoming Callers to a Range of Addresses	Define Site IP Remoteaddress	DEFINE SITE irvine IP REMOTEADDRESS 192.0.1.110 192.0.1.250	Incoming callers will be assigned an IP address between 192.0.110 and 192.0.1.250. Each time the caller successfully connects to the LRS, this address will be assigned. See Specifying IP Address Range for a Site for more information.
Restrict Incoming Callers to a Particular IP Address	Define Site IP Remoteaddress	DEFINE SITE irvine IP REMOTEADDRESS 192.0.1.108	Incoming callers will be assigned IP address 192.0.1.108. Each time the caller successfully connects to the LRS, this address will be assigned. See Specifying Specific IP Address for a Site for more information.
Dynamically Assign IP Addresses to Incoming Callers From an Address Pool	Set/Define IP All/Ethernet Pool	DEFINE IP ETHERNET POOL 192.0.1.50 192.0.1.59	Incoming callers will be assigned a dynamic IP address between 192.0.1.50 and 192.0.1.59. See IP Address Pools for more information.
	Set/Define IP All/Ethernet Proxy-ARP	DEFINE IP ETHERNET PROXY-ARP ENABLED	Enables proxy ARPing; the LRS will respond to ARP requests for the addresses in the pool. See Proxy ARP for more information.
IP Routing
To	Use This Command	Example(s)	What Example Does
Configure a Static Route to Remote Hosts (For Outgoing LAN to LAN Connections)	Set/Define IP Route	SET IP ROUTE 198.8.8.0 NEXTROUTER 192.0.1.9 4	Creates an entry in the IP routing table; packets to 198.8.8.0 will be sent to the router 192.0.1.9. The route will have a metric of 4. See Outgoing LAN to LAN for more information.
Use RIP to Automatically Learn Routing Information	No command needed -- RIP is enabled by default on the default site and all custom sites.
IPX Address Assignment
To	Use This Command	Example(s)	What Example Does
Define the Range of IPX Network Numbers Assigned to the LRS Serial Ports	Set/Define IPX Netrange	DEFINE IPX NETRANGE 0x100	LRS serial ports will be assigned IPX network numbers starting from 0x101, and extending to the sum of 0x100 + the total number of ports. On the LRS16, this range of network numbers is 0x101 to 0x110. See IPX Address Assignment for more information.
IPX Routing
To	Use This Command	Example(s)	What Example Does
Configure a Static Route to Remote IPX Networks (For Outgoing LAN to LAN Connections)	Set/Define IPX Route	SET IPX ROUTE 1234 NEXTROUTER 45af-00-00-ab-12-e2-38.	Creates an entry in the IPX routing table; packets to IPX network 1234 will be sent to router 45af-00-00-ab-12-e2-38. See Outgoing LAN to LAN for more information.
Use RIP to Automatically Learn Routing Information	No command needed -- RIP is enabled by default on the default site and all custom sites.		See Incoming LAN to LAN for more information.
Incoming LAN to LAN and Remote Node (Overall Configuration)
To	Use This Command	Example(s)	What Example Does
Configure Ports	See Chapter 8 - Ports.
Create a Custom Site	Define Site	DEFINE SITE irvine	Creates a custom site named "irvine". See Managing Connections With Sites for more information.
Force Users to Enter a Login Password	1. Set/Define Server Login Password	DEFINE SERVER LOGIN PASSWORD badger	Defines "badger" as the login password. See Login Password and Chapter 11 - Security for more information.
	2. Set/Define Port Password Enabled	DEFINE PORT 2 PASSWORD ENABLED	Incoming callers on port 2 will be forced to enter the login password, "badger".
Force Users to Enter a Username/Password Pair Before PPP/SLIP Runs	1. Define Port PPPdetect Disabled or Set/Define Port SLIPdetect Disabled	DEFINE PORT 2 PPPDETECT DISABLED DEFINE PORT 2 SLIPDETECT DISABLED	Disables autodetection of PPP/SLIP on port 2. See Username/Password Authentication or Automatic Protocol Detection for more information.
	2. Set/Define Port Authenticate Enabled	DEFINE PORT 2 AUTHENTICATE ENABLED	Incoming callers on port 2 will be forced to enter a username/password pair. This pair will be checked against any configured authentication databases. See Username/Password Authentication or Chapter 11 - Security for more information.
Use PAP or CHAP to Obtain the Username and Password From the Incoming Caller	Define Port PPP CHAP Remote or Define Port PPP PAP Remote	DEFINE PORT 2 PPP CHAP REMOTE DEFINE PORT 2 PPP PAP REMOTE	When username/password authentication is required on port 2, PAP or CHAP will be used to obtain the username/password from the remote host. See Username/Password Authentication or Chapter 11 - Security for more information.
Incoming LAN to LAN and Remote Node (Overall Configuration), cont.
To	Use This Command	Example(s)	What Example Does
Configure Authentication Databases	Set/Define Authentication	DEFINE AUTHENTICATION NETWARE PRIMARY bozo_server	Defines the NetWare file server "bozo_server" as the primary authentication database. See Username/Password Authentication or Chapter 11 - Security for more information.
Enable Callers to Start a Custom Site When Entering a Username/Password Pair	Define Site Authentication Local	DEFINE SITE irvine AUTHENTICATION LOCAL "linus"	When an incoming caller is prompted to enter a username/password pair, entering "irvine" and the password "linus" will start site "irvine". See Username/Password Authentication or Chapter 11 - Security for more information.
Outgoing LAN to LAN (Overall Configuration)
To	Use This Command	Example(s)	What Example Does
Configure Ports to Support Outgoing Connections	Set/Define Port Access Remote	DEFINE PORT 2 ACCESS REMOTE	Enables outgoing connections on port 2. See Configure Ports or Access to a Port for more information.
Configure the Modem for Outgoing Calls	1. Define Port Modem Enabled	DEFINE PORT 2 MODEM ENABLED	Enables modem operation on port 2. See Configure Modems or Outgoing Calls for more information.
	2. Define Port Modem Type	DEFINE PORT 2 MODEM TYPE 5	Assigns modem profile 5 to port 2. See Configure Modems or Modem Profiles for more information.
Create a Site to Connect to a Particular Remote Host	Define Site	DEFINE SITE dallas	Creates a custom site named "dallas". See Managing Connections With Sites for more information.
Outgoing LAN to LAN (Overall Configuration), cont.
To	Use This Command	Example(s)	What Example Does
Edit a Site's Configuration	Define Site <characteristic>	DEFINE SITE dallas AUTHENTICATION PAP DISABLED	Disables PAP authentication for site "dallas". See Editing Sites.
Associate a Site With a Port or Ports	Define Site Port	DEFINE SITE dallas PORT 2	Associates site "dallas" with port 2. See Select Port(s) to Use for Dialing Out for more information.
Define the Telephone Number Used to Dial the Remote Host	Define Site Port Telephone	DEFINE SITE dallas PORT 2 TELEPHONE 547-9549	When an outgoing connection attempt is made on port 2 using site "dallas", "547-9549" will be dial the remote host. See Assign A Telephone Number to the Port or Site for more information.
Send a Login Password to the Remote Host	See Chapter 4 - Additional Remote Networking.
Configure a Username and Password to Transmit to a Remote Host	1. Define Site Authentication Username	DEFINE SITE dallas AUTHENTICATION USERNAME "doc_server"	When site "dallas" is used, if the remote host requires that the LRS authenticate itself, the username "doc_server" will be sent. See Configure Authentication or Offering Authentication Information to the Incoming Caller for more information.
	2. Define Site Authentication Remote	DEFINE SITE dallas AUTHENTICATION REMOTE "secret"	The password "secret" will be sent.
Use PAP or CHAP to Transmit the Username and Password to the Remote Host	Define Site Authentication PAP/CHAP	DEFINE SITE irvine AUTHENTICATION CHAP ENABLED DEFINE SITE irvine AUTHENTICATION PAP ENABLED	When the remote host requires that the LRS authenticate itself, PAP or CHAP will be used to transmit the username/password to the remote host. See Configure Authentication or Chapter 11 - Security for more information.
Configure IP/IPX Routing	To configure IP routing, see Chapter 5 - IP. To configure IPX routing, see Chapter 6 - IPX.
Monitoring Connections
To	Use This Command	Example(s)	What Example Does
List Currently Running Sites	Show/Monitor/List Sites	SHOW SITE	Displays all active sites. See Monitoring Networking Activity for more information.
Displays a Site's Configuration	Show/Monitor/List Sites	SHOW SITE IRVINE IP	Displays IP configuration information for site "irvine". See Monitoring Networking Activity for more information.
Displays a Site's Current Performance	Show/Monitor/List Sites Counters	SHOW SITE IRVINE COUNTERS	Displays the current performance of site "irvine". See Monitoring Networking Activity for more information.
Display all Sites that Have Attempted or Completed Connections	Show/Monitor/List Sites Status	SHOW SITE STATUS	Displays statistics for all sites that have been active since the LRS was booted. See Monitoring Networking Activity for more information.

LRS Reference Manual - 4 MARCH 1996

Generated with Harlequin WebMaker