Enter the following command to enable IP forwarding:

TCPIP> SET PROTOCOL IP/FORWARD

To enable IP forwarding in the configuration database, enter the following command:

TCPIP> SET CONFIGURATION PROTOCOL IP/FORWARD

Alternatively, use the sysconfig utility. First, define the TCP/IP Services foreign commands:

$ @SYS$MANAGER:TCPIP$DEFINE_COMMANDS.COM

Enter the following sysconfig commands:

$ sysconfig -r inet ipforwarding=1 $ sysconfig -r inet ipgateway=1 $ sysconfig -q inet

To send notifications automatically on all connected LANs when new hosts or networks become reachable, use dynamic routing with the /SUPPLY option. For example, every time a PPP link is set up to a new subnetwork, RIP (Routing Information Protocol) advertises a corresponding route.

For example, enter the following commands:

TCPIP> START ROUTING /SUPPLY TCPIP> SET CONFIGURATION START ROUTING /SUPPLY

If your PPP and Ethernet interfaces are in the same network, a route is created automatically for the client hosts and an ARP proxy is advertised.

3.2.1.6 Initiating a PPP Connection

You use the OpenVMS PPP utility (PPPD) and associated commands to establish and manage a temporary PPP connection from an OpenVMS Alpha client host to an OpenVMS dialup provider or terminal server. Note that NETMBX and OPER privileges are required to establish a successful connection and to display OPCOM messages.

To invoke PPPD, enter the DCL command PPPD. The PPPD commands are summarized in the following table. For detailed information about PPPD commands and qualifiers, enter the HELP command.

Command	Function
CONNECT	Establishes a network connection through the current physical port or a specified remote port.
DIAL_OUT	Allows direct access to a device in order to dial out over a modem or link to an external device.
DISCONNECT	Terminates the network connection and returns control to the terminal driver.
EXIT	Leaves the utility and returns you to the DCL command prompt ($).
HELP	Displays help text for PPPD commands.
SET	Determines the device and line characteristics for the specified terminal.
SHOW	Displays the device and line characteristics of the specified terminal.

To initiate a PPP connection from an OpenVMS Alpha client to an OpenVMS dialup provider or terminal server, follow these steps.

1. Confirm that you have NETMBX and OPER privileges.
2. Use the PPPD command DIAL_OUT and specify the terminal device. After the atdt command, enter the telephone number of the dialup provider or terminal server. (With some modems, you might need to type the number again until dialing begins.)
   For example:

   $ PPPD PPPD> DIAL_OUT TTA0 Type control-~ to send a break control-\ to disconnect control-@ to switch to a Point-to-Point connection. atdt 8671234

3. If you are connecting to another OpenVMS system, log in to the system after you dial up, and enter the following commands to establish the connection:

   $ PPPD PPPD> CONNECT

   
   To end the connection, enter the DISCONNECT TTn command at the PPPD> prompt and log out.

4. If you are connecting to a terminal server, enter the CONNECT PPP prompt at the LOCAL> prompt. An informational message will confirm the PPP connection:

   LOCAL> CONNECT PPP Local -561- Starting SLIP or PPP datalink session %PPPD-I-CONNECTTERM, converting connection on device _TTA0: to a Point-to-Point connection

   
   To end the connection, enter DISCONNECT TTn at the PPPD> prompt. After the connection is terminated, an OPCOM message is displayed. For example:

   %%%%%%%%%%% OPCOM 23-APR-1998 15:44:32.10 %%%%%%%%%%% Message from user XYZnet on JONES %TCPIP-S-PPPDISCONN, Disconnected PPP Interface PP1 on TTA0

To remove the PPP configuration, follow these steps:

1. If you created a PPP interface, return the associated terminal port to general use. Enter:

   TCPIP> SET NOINTERFACE PPn

   
   In this example, n is the number of the interface. If you omit the interface number, PP0 is assumed.

2. If you added special route and proxy entries with the PPP line, remove them.
3. If you changed any terminal settings in preparation for PPP, restore them. Enter the DCL command SET TERMINAL, and wait for the modem to reset and free the port and phone line.

Configuring the network interface for SLIP is the same as configuring the interface for Ethernet connections. In this case, the network interface is the modem connection. Remember that before you can configure a SLIP line, you must choose an IP address for the interface at each end of the line and establish a physical connection.

Use the following commands to set up the SLIP interface:

• SET INTERFACE SLn, where n is the number of the interface. If you omit the interface number, SL0 is assumed. This command takes effect immediately and stays in effect until the next TCP/IP Services shutdown.
• SET CONFIGURATION INTERFACE SLn, where n is the number of the interface. If you omit the interface number, SL0 is assumed. This command makes the change part of the permanent configuration. The change takes effect at the next product startup.

Table 3-3 describes the command qualifiers used for configuring SLIP interfaces.

Table 3-3 Command Qualifiers Used for Configuring SLIP

Qualifier	Description
/[NO]AUTO_START	Optional. The default is /AUTO_START. Automatically creates the interface on startup.
/COMPRESS=[ON|OFF|AUTOMATIC]	Optional. The default is no compression. Enables or disables TCP header compression (CSLIP). With /COMPRESS=AUTOMATIC, compression remains off unless the remote host begins to use it.
/[NO]FLOWCONTROL	Optional. The default is No flow control. Enables the special handling of XON and XOFF characters to work properly with modems that are configured to interpret these characters locally. Specify /FLOWCONTROL only if the host at the other end of the line is another host running TCP/IP Services. If you cannot use /FLOWCONTROL, configure your modem to pass all the XON and XOFF characters through transparently.
/HOST=( host_name, IP_address)	Required. Host name or IP address of the local host. If your host is multihomed, you must specify an address in dotted-decimal notation.
/NETWORK_MASK= subnet_address	Required. The subnet mask of the local SLIP interface in dotted-decimal notation.
/SERIAL_DEVICE= device	Required for hard-wired or dedicated modem connections. Optional for dynamic connections. Identifies the OpenVMS device name assigned to the SLIP interface, for example, TTA1.

For example, the following command configures SLIP interface SL5, using the local IP address assigned to host CROW, with a subnetwork mask of 255.255.255.0. The interface uses the terminal device TTA3:. The /COMPRESS qualifier enables TCP header compression (CSLIP). The /FLOWCONTROL qualifier enables special handling of XON and XOFF characters.

TCPIP> SET INTERFACE SL5 /HOST=CROW /NETWORK_MASK=255.255.255.0 - _TCPIP> /SERIAL_DEVICE=TTA3 /COMPRESS=ON /FLOWCONTROL

3.3.1 Setting Up Hard-Wired SLIP Lines

To configure SLIP with hard-wired lines, follow these steps:

1. Establish a physical connection. Plug in a serial cable between the two host systems or ensure that they are both cabled to opposite ends of a leased line.
2. Obtain an IP address if necessary.
3. Configure the SLIP interface. Enter the SET INTERFACE command with the /HOST and /SERIAL_DEVICE qualifiers, which are required.

You can configure either a terminal server port or an OpenVMS system to answer dialin calls.

Follow these steps:

1. Configure the appropriate settings for the terminal port to which you will connect. Begin a dialog of dialing (or answering) commands with your modem. The specific required commands depend on the type of modem you are using.
   For example, to prevent the modem from hanging up when you exit the DTE session to bring up the SLIP line, enter the following command:

   $ SET TERMINAL TTA2 /PERMANENT /MODEM /NOHANGUP

   
   To disable interactive logins on the line, enter the following command:

   $ SET TERMINAL TTA2 /PERMANENT /NOTYPEAHEAD

   
   Any SLIP data that arrives before you enter the SET INTERFACE command is ignored. Otherwise, this command triggers the creation of a new interactive login process.
   To enable interactive logins after a user sends a Break, enter the following command:

   $ SET TERMINAL TTA2 /PERMANENT /NOAUTOBAUD /SECURE_SERVER

2. Configure the modem. Enter the appropriate commands to dial the telephone and establish communication.
3. Unless you are setting up a SLIP line between two hosts running TCP/IP Services and plan to use the /FLOWCONTROL qualifier at both ends, disable modem recognition of XON and XOFF characters. (If SLIP packets have Ctrl/S and Ctrl/Q characters embedded in them as data, you must prevent the modem from trying to interpret these characters.)
   Either use hardware flow control or disable flow control entirely. The following examples disable all flow control.
   • With a DECmodem V32 in AT command mode, set the following values:
     • AT%F0 --- No speed buffering flow control
     • AT%M0 --- Disable speed buffering (optional)
   • With a DECmodem V32 in DMCL mode, set the following values:
     • SET P2/SBU
     • SET P1/SBU
     • prompts appropriate_answers
   • With a U.S. Robotics Sportster modem, set the following values:
     • AT&B0 --- Variable, follows connection rate (optional)
     • AT&H0 --- Flow control disabled
     • AT&I0 --- Software flow control disabled
4. Obtain IP addresses if necessary.
5. To dial in, follow these steps:
   1. Enter the SET HOST /DTE command:

      $ SET HOST /DTE nx

   2. Type the telephone number. For example:

      atdt telephone_number

   3. The connected system displays its interactive (command mode) prompt. You are talking to the terminal server and can now make the connection.

The following example shows a user named SLIP-USER at a PC named ROBIN with a 9600-baud modem, using terminal device TTA2 and connecting it to the port of a terminal server. In this example:

• The terminal server is a DECserver 700 terminal server.
• The user directs the modem to dial the telephone number 222-2222.
• The password prompt of the terminal server is # .
• The terminal server's current login password is hootowl .
• The terminal server's prompt is Local> .
• The user types Ctrl/\ (Ctrl key plus backslash) to escape from the terminal server to the SLIP host.
• The user defines interface SL2 and identifies it as SLIP device TTA1: with IP address 1.2.3.4. Communication on this line will use CSLIP.

$ SET HOST /DTE TTA2 %REM-I-TOQUIT, connection established Press Ctrl/\ to quit, Ctrl/@ for command mode atdt 2222222 CONNECT 9600 # hootowl (not echoed) Network Access SW V1.5 for DS700-16 (c) Copyright 1994, Digital Equipment Corporation - All Rights Reserved Please type HELP if you need assistance Enter username>SLIP-USER Local> CONNECT SLIP Ctrl/\ TCPIP> SET INTERFACE SL2 /HOST=1.2.3.4 /NETWORK_MASK=255.255.255.0 - _TCPIP> /SERIAL_DEVICE=TTA1: /COMPRESS=ON

3.3.3 Setting Up Your Host as a SLIP Dialup Provider

You can configure your host to answer calls and establish connections initiated by users on remote hosts.

To set up your host as a SLIP provider:

1. Over the line you will define as a SLIP line, dial in to the host.
2. Log in to the remote host.
3. Enter an appropriate SET INTERFACE command with the /SERIAL_DEVICE qualifier to turn the line into a SLIP line.
   For example, the following command creates a SLIP interface named SL5, using the terminal device associated with the session where the command is entered.

   TCPIP> SET INTERFACE SL5 /HOST=192.208.35.5 /SERIAL_DEVICE=TT

4. Log out.

As soon as you log out, your terminal port becomes a SLIP interface. Without causing the modem to hang up, start SLIP on the remote system.

To facilitate connection setup for end users, create a dedicated user name for each remote host that dials in. These users need to have a LOGIN.COM procedure that invokes appropriate SET TERMINAL commands and TCP/IP management SET INTERFACE commands, terminating with a LOGOUT command. Every user should specify a different SLIP interface name and host name (or IP address). These users require the OPER privilege to create interfaces.

You can enable IP forwarding on the SLIP provider host and start dynamic routing. For example, enter the following commands:

TCPIP> SET PROTOCOL IP /FORWARD TCPIP> SET CONFIGURATION PROTOCOL IP /FORWARD

To send notifications automatically on all connected LANs when new hosts or networks become reachable, use dynamic routing with the /SUPPLY option. For example, every time a SLIP connection is set up to a new remote subnetwork, RIP (Routing Information Protocol) advertises a corresponding route. For example, enter the following commands:

TCPIP> START ROUTING /SUPPLY TCPIP> SET CONFIGURATION START ROUTING /SUPPLY

3.3.4 Connecting a Host to the LAN

You can make your SLIP-connected host appear as if it were directly connected to the LAN. This is possible using a proxy ARP server (usually the same host that is acting as a SLIP gateway into the LAN).

To use proxy ARP (Address Resolution Protocol), assign to the remote host an IP address in the same subnetwork as the LAN. As other hosts on the LAN attempt to communicate with the remote host, the SLIP gateway answers ARP queries for the remote host by giving its own LAN address. The gateway then forwards packets across the SLIP line.

Many DECserver terminal server products support SLIP connections and implement proxy ARP. If you dial in from an OpenVMS host to a terminal server, the terminal server automatically detects your IP address and begins responding to ARP queries, forwarding packets as necessary.

To use proxy ARP with a DECserver terminal server, assign an IP address in the same subnetwork as the terminal server.

At the terminal server, enter the TCP/IP management command SHOW PORT SLIP. Verify that:

• An IP address has not already been associated with your port.
• Header compression is available, if you plan to use it.

It is also possible to set up your host as a SLIP gateway with proxy ARP. You might prefer this approach if your dialin modems are attached directly to an OpenVMS system rather than to a terminal server.

Follow these steps on the host to become a SLIP gateway:

1. Create a SLIP interface in another network or subnetwork, for example:

   $ TCPIP SET INTERFACE SL0 /HOST=10.1.2.3 /SERIAL_DEVICE=TTA2

2. Add a host route for the remote system. For example:

   $ TCPIP SET ROUTE FINCH /GATEWAY=10.1.2.3

3. Configure an ARP entry for the remote host, listing your own Ethernet address (as shown in TCPIP SHOW INTERFACE /FULL). For example:

   $ TCPIP SET ARP 08-00-2B-2C-4F-46 FINCH /PUBLIC

4. Enable IP packet forwarding, if not already done. Enter:

   $ TCPIP SET PROTOCOL IP /FORWARD

When your host is set up as a SLIP gateway, create an interface on the remote host at the other end of the serial line. Specify an address in the same subnetwork as the LAN.

Although the two ends of the SLIP line are in different subnetworks, traffic can flow properly due to the interface route you added with the SET ROUTE command.

3.3.6 Shutting Down SLIP

To terminate a SLIP connection, follow these steps:

1. Return the associated terminal port to general use. Enter:

   $ TCPIP SET NOINTERFACE interface

2. If you added special route and proxy entries in conjunction with the SLIP line, remove them.
3. If you changed any terminal settings in preparation for SLIP, restore them using the SET TERMINAL command.

If you have problems dialing in to an OpenVMS system using SLIP or PPP after following the instructions in this chapter, perform the following steps to isolate the cause of the problem:

1. Check the equipment used by both the client and the dialin provider:
   • Do the cables work?
   • Are the modems configured properly?
   • Are the DIP switches on the modems set correctly?
   • Are the modem software settings correct? Make sure that flow control is disabled.
   • Are all clients and dialup providers using unique addresses?
   
   After a software upgrade, be sure to reboot and restart TCP/IP Services.
2. Make sure the SET HOST attempts have not exceeded the OpenVMS security level. To check and then delete, if necessary, any information about these attempts, enter the following commands. Note that SECURITY privilege must be enabled to use these commands.

   $ SHOW INTRUSION $ DELETE/INTRUSION_RECORD source

3. Make sure that IP forwarding is enabled using the following command:

   TCPIP> SHOW PROTOCOL IP/FORWARD

4. Make sure the terminal characteristics for the terminal device associated with the interface are set up as follows:

   $ SET TERMINAL TTnx /ALTYPEAHD /AUTOBAUD /DIALUP - _$ /DISCONNECT /EIGHTBIT /MODEM /NOHANGUP /NOHOSTSYNC /NOPASTHRU - _$ /NOREADSYNCH /NOTTYSYNCH /PERMANENT /TYPE_AHEAD

   
   Make sure you specify the /TYPE_AHEAD qualifier when you enter the SET TERMINAL command to set up an asynchronous port.

5. Enter the SET HOST/DTE command to make sure you can log in to the system:

   $ SET HOST/DTE TTnx

   
   If you cannot log in to or communicate with the system, you may be using the wrong terminal device name (TTnx).

6. Set up OPCOM to receive messages using the DCL command REPLY/ENABLE. You need OPER privileges to use OPCOM.
7. You need NETMBX and OPER privileges to establish a successful connection. If these privileges are not enabled when you enter the CONNECT command, you will see messages similar to the following:

   $ PPPD PPPD> CONNECT \}`}"}(}"6~ <CTRL/@> %PPPD-I-CONNECTTERM, converting connection on device _TTA0: to a Point-to-Point connection %PPPD-E-CALLBACKERR, error calling network callback %SYSTEM-F-NOPRIV, insufficient privilege or object protection violation %PPPD-F-ABORT, fatal error encountered; operation terminated

   
   Note that the extraneous data in this sample is an ASCII representation of IP packets transmitted over the open line.
   PPP sets up a default route on the client if one did not exist. Typically, a default route exists if another interface exists on the client.

8. Attempt to ping the remote system:

   TCPIP> PING host-name

   
   Watch the modem's LED display as you attempt to communicate using the PING command.
   You might not be able to ping the system if the serial line is tied up with a large FTP operation.

9. Use the TCPTRACE command to see packets going in and out of the local system. For information about using TCPTRACE, enter:

   $ HELP TCPTRACE

10. Display a count of the packets being sent and received on the problem interface, in full screen format, updated every second. For a SLIP problem, enter:

    TCPIP> SHOW INTERFACE SLn

    
    To display the packet counts for PPP problem, enter:

    TCPIP> SHOW INTERFACE PPn

    
    In these commands, n is the interface number.