Previous Page: Remote IPX Nodes  Next Page: Remote AppleTalk Nodes

Remote IP Nodes

Loading PPPRNS with IP support allows IP clients to dial in and become remote nodes on the network. This procedure adds the appropriate LOAD and BIND commands to the NETINFO.CFG file.

Table 9 describes the IP parameters that you configure for PPPRNS with IP support.


Table 9. PPPRNS IP Parameters

Parameter Description

Local IP Address

Specifies the local IP address for the WAN interface on the remote access server. This is a 4-byte (32-bit) numeric value that identifies both a network and a local host or node on that network. The address is represented in dotted decimal notation. Each byte is represented by a decimal number, with periods separating the bytes, for example, 130.57.45.240. Each byte can range from 0 through 255. Do not use hexadecimal numbers.

The local IP address must be on the same subnet as the client address range. The remote access software creates a virtual LAN segment (network) for all IP clients accessing this server.

The IP address on the remote node can be configured statically or dynamically:

Statically---The user explicitly specifies the IP address in the client software.

Dynamically---The remote access software assigns IP addresses through IPCP. Specify a client range.

Dynamically---The remote access server is a BOOTP server and assigns IP addresses. Configure the remote access server as a BOOTP server.

Subnet Mask

A 4-byte numeric value in dotted decimal notation. Each byte ranges from 0 through 255, with periods separating the bytes.

Use Header Compression

Specifies whether to use header compression over the WAN link with the remote client. The default is No.

If you specify Yes, the remote access IP service will use TCP header compression with all remote access clients connecting to this address. Make sure that the settings for header compression on the server and the client agree: both are enabled or both are disabled. If the client is not configured to use header compression but the server is, TCP will not run between the remote access server and the client.

Specify Client Address Range

Specifies whether the remote access software assigns IP addresses to the remote nodes. Once you have specified the range and a client requests an address, remote access chooses an address that is not in use by another client from the address range and assigns it to the requesting client.

Address assignments can be made through either IPCP (Internet Protocol Control Protocol) or BOOTP if the remote access server is configured as a BOOTP server. If the remote access server is not configured as a BOOTP server and a client address range is specified, IPCP address assignment is used.

Client Address Range Start

Specifies the starting address for the remote IP client address range. The client address range must be on the same network or subnet as the server address specified in the Local IP Address parameter.

Client Address Range End

Specifies the ending address for the remote IP client address range.

Specify Secondary Client Address Range

Note: You configure a user to use the primary or secondary client address range with the NetWare Administrator utility. The secondary client address range feature might or might not be available on your system; it is an optional part of the standard Novell Internet Access Server 4.1 software.

Secondary Local IP Address

Specifies an additional (secondary) local IP address on the remote access server.

Secondary Subnet Mask

Specifies an additional (secondary) subnet mask on the remote access server.

Secondary Address Range Start

Specifies the starting address for the secondary remote IP client address range. This is a separate group of addresses that you can specify to limit or restrict access to network locations.

Secondary Address Range End

Specifies the ending address for the secondary remote IP client address range. This is a separate group of addresses that you can specify to limit or restrict access to network locations.

To load PPPRNS with IP support, complete the following steps:

  1. Load NIASCFG, then select the following path:

    Select Configure NIAS > Remote Access > Set Up... > Select Remote Access Services > PPPRNS > IP

  2. Select Local IP Address and enter a valid, unique local IP address.

    NOTE:  The local IP address must be on the same subnet as the client address range.

  3. Select Subnet Mask and enter a 4-byte value in dotted decimal notation.

  4. Select Use Header Compression, then specify Yes to use TCP header compression. Otherwise, specify No.

    NOTE:  Make sure the settings for header compression on the server and the client agree, that is, both are enabled or disabled.

  5. Select Specify Client Address Range and do the following:

    NOTE:  The Client Address Range parameters must be set when the remote access server is configured as a BOOTP server.

    1. Specify Yes if you want the remote access server to assign IP addresses to the remote nodes. Otherwise, specify No and continue with Step 6.

    2. Specify the Client Address Range Start and Client Address Range End parameters.

    NOTE:  The address range is for address assignment only, and is not for authenticating the remote IP address. If the client already has an address configured locally and does not need address assignment from the remote access server, the remote access software will not check the client address against the address range to make sure it is within the range.

  6. (Optional) Select Specify Secondary Client Address Range and do the following:

    1. Specify Yes if you want the remote access server to assign secondary IP addresses to the remote nodes. Otherwise, specify No and continue with Step 7.

    2. Specify the Secondary Subnet Mask, Secondary Address Range Start, and Secondary Address Range End parameters.

    NOTE:  The secondary address parameters might not be available on your system. If these parameters are available, you can use them to limit access to certain network locations.

  7. Press Esc and specify Yes to save your changes.

    The service is selected, but is not necessarily running. When a service is selected, it is added to the NWCSTART.NCF file. To verify that the service is running, you can view service statistics, as described in Viewing Service Statistics.

The changes take effect the next time you start the PPPRNS service.

Once you have completed the procedure to support remote IP nodes, you can do the following:



  Previous Page: Remote IPX Nodes  Next Page: Remote AppleTalk Nodes