Configuring IPTUNNEL

  • 10014154
  • 4.0.19951375.2271773
  • 12-Aug-1999
  • 17-Feb-2003

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Goal

Configuring  IPTUNNEL

Fact

Need IPX communication over IP

Fix

IP Tunneling for IPX
IPX uses the Open Data-Link InterfaceTM (ODITM) interface to pass packets through the IP tunnel. The IP tunnel sends each IPX packet across the TCP/IP network by encapsulating it in a User Datagram Protocol (UDP) packet. The tunnel driver at the destination router removes the UDP header from each incoming packet and passes it through ODI to IPX.

Encapsulating IPX packets in IP packets enables them to go through any TCP/IP supported media, such as Ethernet or token ring.

The TCP/IP network is the medium. The IP address is the immediate address that performs the same function in the TCP/IP medium as the media access control (MAC) address performs in the Ethernet medium.

IPTUNNEL---LAN driver that models the IP internetwork as a single IPX LAN to tunnel IPX packets.

To configure your router to use an IP tunnel, IP must be loaded and bound to the interfaces you plan to use. The IP tunnel requires local IP addressing information, and can fail if IP is not bound to the network interface. For basic IP configuration procedures, refer to 'Configuring IP.'

The IPTUNNEL Driver
You can also use the IPTUNNEL driver to enable IPX to use a TCP/IP network to communicate with other IPX nodes. You configure IPTUNNEL from the INETCFG or from the command line.

The IPTUNNEL driver enables IPX to use a TCP/IP network to communicate with other IPX nodes. The IPTUNNEL driver models the IP internetwork as a single IPX LAN. To IPX, IPTUNNEL performs the same functions as a typical NetWare® LAN driver. The TCP/IP network operates as if it were a hardware network, passing packets among the IPX nodes connected to it.

IPTUNNEL is compatible with the Schneider & Koch SK-IPX/IP Gateway, which provides NetWare 2 compatibility. IPTUNNEL also serves workstations using either the Novell IP tunnel workstation driver, a component of the LAN WorkPlace® for DOS software, or the Schneider & Koch end node product for DOS.

When configuring the IP tunnel, you supply the IP addresses of other IPX routers that you plan to include in the tunnel. These other IPX routers are known as peers. Whenever IPX broadcasts a packet, the IP tunnel duplicates the packet and sends a copy to each peer.

To exchange routing and service information between IPX routers, IPX depends on broadcasting messages to every other NetWare server connected to the medium. However, because broadcast facilities are limited in TCP/IP networks, IPTUNNEL must handle broadcast traffic by duplicating the packet and sending a copy to each peer router.

IPTUNNEL presents a standard ODI driver interface to the NetWare system and handles IPX traffic like any other driver. You load the driver like any other, and then bind IPX to it to instruct IPX to receive and route packets over the TCP/IP network.

IMPORTANT: You should configure any connected group of peers so all servers in the group have the IP addresses of all other servers in the group. Other configurations are possible but not recommended; they frequently create confusing, and often surprising, IPX routing topologies.

Compatibility Between IPTUNNEL and IPRELAY
IPRELAY is compatible with IPTUNNEL. IPRELAY accepts packets from a LAN set up with IPTUNNEL as long as one of the routers on the LAN is running RIP.

Because IPRELAY allows point-to-point connectivity with the NetWare Link Services ProtocolTM (NLSPTM) software, NLSP operates more efficiently with IPRELAY than with IPTUNNEL. NLSP operates reliably over point-to-point connections; therefore, it has lower periodic traffic requirements.

Because IPRELAY works like any WAN driver, you can initiate and terminate IPRELAY connections from the Call Manager utility (CALLMGR). You can also use CALLMGR to reestablish lost IPRELAY connections. Additionally, CALLMGR identifies IPRELAY-to-IPTUNNEL connections with a '(T)' next to the remote peer IP address.


Configuring I.PTUNNEL from INETCFG
Before you configure IPTUNNEL, you must make sure that TCP/IP is enabled and bound to the interface.

To configure the IPTUNNEL driver, complete the following steps:

Load INETCFG,

Select Boards > Press Ins

Select IPTUNNEL from the list.

The Board Configuration menu is displayed.

Configure the Board Name parameter.

Enter a valid address for the Peer IP Address parameter.

If this parameter is not present, no peer is added. This is the most important parameter.

If needed, enter a value for the Local IP Address parameter.

For IPX routing to work correctly, the IP tunnel must use a single local IP address consistently. The default value is the IP address of the first interface to which TCP/IP was bound.

Set the UDP Checksum parameter to Yes.

Enabling this parameter improves data reliability.

If needed, enter a value for the UDP Port parameter.

If you must communicate with nodes using products prior to Schneider & Koch SK-IPX/IP version 1.3, you can use port=59139. Otherwise, use the default value of 213, which is the officially assigned UDP port for IPX packets.

Press Esc.

The new board appears at the end of the list on the Configured Boards screen.

Press Esc to return to the Internetworking Configuration menu.

Configure IPX and bind it to IPTUNNEL.

Press Esc to return to the Internetworking Configuration menu; save your changes when prompted.

If you want these changes to take effect immediately, restart the server (you can use the command REINITIALIZE SYSTEM, but that sometimes does NOT fully initialize the new parameters).

If you want to configure other parameters, do so now; then restart the server when you are finished.

Configuring IPTUNNEL for Multiple Peers

IMPORTANT: IPTUNNEL duplicates and transmits every IPX broadcast packet in a UDP packet to each remote peer in a peer group. Because this can create a large amount of traffic on the network, you should have no more than ten  peers for any one node. We recommend that you use IPRELAY with NLSP for situations with more than 10 peers.

To configure IPTUNNEL for multiple peers, you must use LOAD and BIND commands from the command line as described below.

As an example:
Server A: IP Address-1.0.0.3 IPX Net-37
Server B: IP Address-129.1.0.7 IPX Net-54
Server C: IP Address-192.1.1.96 IPX Net-83
IP Tunnel: IPX Net-95

To configure IPTUNNEL on Server A, you enter the following commands at the Server A console:

LOAD IPTUNNEL PEER=129.1.0.7
LOAD IPTUNNEL PEER=192.1.1.96
BIND IPX to IPTUNNEL NET=95
The first two commands load IPTUNNEL and add entries on Server A for peer IP addresses 129.1.0.7 (Server B) and 192.1.1.96 (Server C). The third command binds IPX to IPTUNNEL.

To configure IPTUNNEL on Server B, you enter the following commands at the Server B console:

LOAD IPTUNNEL PEER=1.0.0.3
LOAD IPTUNNEL PEER=192.1.1.96
BIND IPX to IPTUNNEL NET=95
The preceding commands are almost identical to those in the Server A configuration. These commands add entries for peer IP addresses 1.0.0.3 (Server A) and 192.1.1.96 (Server C) and bind IPX to IPTUNNEL.

To configure IPTUNNEL on Server C, you enter the following commands at the Server C console:

LOAD IPTUNNEL PEER=1.0.0.3
LOAD IPTUNNEL PEER=129.1.0.7
BIND IPX TO IPTUNNEL NET=95
The preceding commands are almost identical to those in the Server B configuration. These commands add entries for peer IP addresses 1.0.0.3 (Server A) and 129.1.0.7 (Server B) and bind IPX to IPTUNNEL.

If needed, you can configure additional parameters with the LOAD IPTUNNEL command using the following format:

LOAD IPTUNNEL [PEER=remote IP address]|[LOCAL=local IP address]|[CHKSUM={YES|NO}]|[PORT=UDP port number]|[SHOW={YES|NO}]

NOTE: If you configure IPTUNNEL for multiple peer routers, use the LOCAL and PORT parameters only with the first LOAD IPTUNNEL command.

The SHOW parameter, available only with the command-based configuration, displays an IPTUNNEL configuration summary. If you load IPTUNNEL with SHOW set to YES (the default), the command displays the local IP address, the UDP port used, the peer list, and whether UDP checksums are enabled.

.