- The routing software can be used to set up a PPP connection to an Internet Service Provider (ISP) provided there is TCP/IP routing to the Internet over a dial-up modem, ISDN card, or synchronous WAN link.
- Some configuration options require special attention when connecting to an ISP. Ensure that you have already configured the appropriate board and interface for a PPP connection. Also, obtain a PPP account with an ISP and at least one assigned STATIC IP address. The routing software currently does not support dynamically assigned local addresses.
- If you will be routing to a local LAN that uses IP addresses, these addresses must also be obtained from your ISP, or otherwise registered with your company. You cannot make up your own addresses.
- Asynchronous modems on a serial port use the driver WHSMAIO. CAPI-compliant ISDN boards use the driver WHSMCAPI. All other boards have a board-specific driver. Novell Internet Access Server 4.1 does not currently support ISDN modems or Terminal Adapters. Check with the manufacturer to see if it provides its own ISDN scripts for the Novell Internet Access Server 4.1 routing software.
- For WAN interface configuration, set Interface Speed to External if you are using DSU/CSU devices. Disable Inbound Authentication under Authentication Options because you will be originating the call. Under Negotiation Options, set PPP Header and Data Compression to Disabled. To make these changes, load NIASCFG and select Configure NIAS > Protocols and Routing > WAN Call Destinations > select the WAN Interface Driver. Changes can be made in the ISDN Parameters and Special Options windows. You can enable these options later if your ISP supports compression.
- Your ISP should inform you if you must use a login script. Login Script Name allows you to select a script that can be used to specify a login name, a password, or other keywords expected by your ISP. Some ISPs might require this type of exchange before you access their system, or they might require that you inform them that you will be using PPP. These steps might be necessary if you must actually log in to the ISP's system or send data through a firewall. In most cases, a login script is not necessary. You probably will be given a username and password by your ISP, but this information is used later in the Outbound Authentication setup.
- The Outbound Authentication option in NIASCFG (parameter path: Select Configure NIAS > Protocols and Routing > WAN Call Directory > ISDN Interface Driver > Outbound Authentication) specifies the PPP authentication protocol to be used. On-demand links require authentication, but it is optional on permanent links. The type of authentication is determined by the ISP.
For on-demand links, set Outbound Authentication to either PAP or CHAP. Either type of authentication is used, depending on the ISP requirements. If you are setting up a permanent link and are certain that the ISP uses no authentication, set Outbound Authentication to None.
The ISP will give you a PAP or CHAP login name and password (the ISP might refer to it as your account username and password). For Local System ID, enter the username or login name assigned to you by the ISP. The username and password are case-sensitive. For Remote System ID, enter a name you want to use to identify the remote system. This can be any name, such as ISP.
- For TCP/IP protocol configuration, load NIASCFG (parameter path: Select Configure NIAS > Protocols and Routing > TCP/IP). Make sure that both TCP/IP Status and IP Packet Forwarding are enabled. Other settings can be left at their defaults.
- If you plan to bind TCP/IP to the WAN interface, your ISP should have assigned you an IP address for your side of the link and/or a block of addresses for your own use. The binding configuration will vary, depending on the addresses assigned to you and the type of link the ISP has set up. There are two ways the link can be set up: numbered single point-to-point and unnumbered single point-to-point.
- Numbered single point-to point---This type of connection uses an IP address for each end of the WAN link. The link is treated as its own network, so the two IP addresses must conform to the same network address. An example follows:
Local IP address: 137.65.45.17 (subnet mask 255.255.240)
Remote IP address: 137.65.45.19 (subnet mask 255.255.240)
Block of addresses: 150.3.56.64 through 150.3.56.95 (subnet mask 255.255.255.224)
The local and remote IP addresses for the WAN link are in the same network. If the local and remote IP addresses are not in the same network, do not use a numbered link. Set up a numbered link and bind 137.65.45.17 to the WAN interface and specify 137.65.45.19 as the remote IP address. Use the block of addresses assigned to you to bind to the network interface in the server and the clients on the LAN.
To configure a numbered single point-to-point connection, load NIASCFG, select Configure NIAS > Protocols and Routing > Bindings, and then press Ins to add a new binding. Select TCP/IP and then select the WAN interface set up previously. For WAN Network Mode, select Numbered Single Point-to-Point. For Local IP Address, enter the local IP address assigned by the ISP (for example, 137.65.45.17). For Subnetwork Mask, enter the subnet mask assigned by the ISP (for example, 255.255.255.240). Select WAN Call Destination, then press Ins . Press Enter and select the defined WAN call destination. For Remote IP address, enter the ISP's remote address (for example, 137.65.45.19). Press Enter on Static Routing Table and then press Ins to add a new static route. Under Route to Network or Host, select Network for the IP Address of Network/Host and enter 0.0.0.0 . The static routing entry sets up a default route that points to the ISP. Leave all other settings at their defaults values.
- Unnumbered single point-to-point---This type of connection does not use an IP address for either end of the WAN link. No IP address is bound to the WAN interface. Instead, it is bound to the local NIC in the routing software. The local IP address bound to the NIC is on a network different from the one that the remote IP address of the ISP is on. Sample ISP-provided addresses follow:
Local IP addresses: 150.3.56.64 through 150.3.56.95 (subnet mask 255.255.255.224)
Remote IP address: 137.65.45.19 (subnet mask 255.255.255.240)
Because the local and remote IP addresses for the WAN link are in different networks, you must use an unnumbered WAN link. Bind the local address (or the first address in a block of addresses) to the local NIC.
To configure an unnumbered single point-to-point connection, load NIASCFG and select Configure NIAS > Protocols and Routing > Bindings. Press Ins to add a new binding. Select TCP/IP and then select the WAN interface set up previously. For WAN Network Mode, select Unnumbered Single Point-to-Point, then select WAN Call Destination and press Ins . Press Enter and select the WAN call destination defined earlier. Press Enter on Static Routing Table and press Ins to add a new static route. Under Route to Network or Host, select Network for the IP Address of Network/Host and enter 0.0.0.0 . The static routing entry sets up a default route that points to the ISP. Leave all other settings at their default values.
- After you have completed the setup, reinitialize your system and test the WAN link. Load CALLMGR.NLM at the server console. For a permanent link, the call should come up automatically with a status of Out-Connecting, then Out-Connected. A console message appears stating that an IP connection was established to the WAN call destination. For an on-demand link, bring up the link manually. Press Ins , select WAN Call Destination, and select IP. The status should show Out-Connecting, then Out-Connected. A console message appears stating that an IP connection was established to the WAN call destination. Load PING.NLM at the server console and enter the IP address of the ISP. Press Esc to begin the ping. Packets should be sent and received. The IP clients connected to the LAN side of the routing software server should also be able to access the Internet through the router's WAN link.
- To route IPX over a WAN, you must always bind IPX to a WAN board.
- You can define only one WAN call destination for all protocols going to the same destination. Each protocol can use the same WAN call destination name when it is bound to the WAN interface.
- When routing IPX or AppleTalk over a permanent PPP link, you must specify the permanent WAN call destination under Bindings on only one side of the WAN connection (the originating side).
- When routing AppleTalk or IPX over an on-demand PPP link, you must specify a WAN call destination in the static routes or static services configuration on both sides of the WAN connection (parameter path: Select Configure NIAS > Protocols and Routing > Bindings > a specific binding > WAN Call Destination > Static Routes).
- When using IP RIP over a WAN in Multi-Access mode, you must configure at least one neighbor in the Neighbor List option in NIASCFG (parameter path: Select Configure NIAS > Protocols and Routing > Bindings > Select a specific TCP/IP binding > Expert TCP/IP Bind Options/RIP Bind Options).
- When configuring source route bridging over a WAN, make sure that you enable and configure the route end station on all WAN ports that allow clients to access the NetWare file server. If the node is a dedicated router, the route end station is not required.
- When you are routing or source route bridging over NetWare Link/PPP, you must configure a WAN call destination.
- If your DCE device (DSU/CSU, modem, multiplexer, and so on) has both single and dual clocking configuration options, make sure you configure your DCE to provide both transmit and receive clocks when a Synchronous/+ or NW2000 board is being used.
