Protocols Tab

Usage: Click the Help button at any time to get online help for the settings in the current tab.

This opens a World Wide Browser, such as Netscape Navigator or Internet Explorer, and displays information about the settings.

To close the help display, close the browser as you would any other program. For example, in Windows 95, click the X button at the upper right of the window or choose Exit from the File menu.

With some browsers, a new window will open each time you click the Help button. If this happens, simply close each window when you're done with it.

Finding setting descriptions: At the beginning of each help window is a table of contents for the window. To go to information about a particular setting, click the hyperlink (the underlined text in most browsers) for that setting in the contents. To return to the contents, use the control in your browser for going back, such as the Back button in Netscape Navigator or Internet Explorer 3.0.

Usage: Click this button to send the settings shown in the Java-Based Pipeline Configurator to the Pipeline.

These new settings replace the previous settings in the Pipeline. You can use this button at any time; you do not have to enter values for all settings before updating the Pipeline.

Usage: Click this to save the settings shown in the Java-Based Pipeline Configurator in a file on your computer.

You then use your operating system's facility for specifying a name and location for the file, such as the Save To dialog box in Windows 95.

You can later open a file in which you've saved settings by clicking the Open a Configuration File button in the first window that appears when you run the Java-Based Pipeline Configurator.

You can use this button at any time; you do not have to enter values for all settings before saving settings.

Usage: Choose one of the following:

• IP

  This displays Internet Protocol (IP) settings. These settings are described in the IP settings section.

• IPX

  This displays IPX settings for Novell NetWare networks. These settings are described in the IPX settings section.

Usage: Check the box to enable bridging of protocols that are not routed.

Dependencies: Keep this additional information in mind:

• For bridging to occur, bridging must be enabled on the device to which you're connecting as well as on the Pipeline.

• For bridging to occur, the Enable Bridging checkbox for the current connection profile (viewable by opening the Connections tab, opening a connection profile, and then clicking the General button) must also be checked.

Usage: Enter the IP address of the Pipeline on the local Ethernet network.

The address consists of four numbers between 0 and 255, separated by periods. The IP address must be a valid IP address on the local Ethernet network.

Example: 10.2.1.1

Dependencies: Keep this additional information in mind:

• The value of the IP Address setting must match the IP Address setting expected by the device to which the Pipeline connects.

• If you do not know the right IP address to enter, you must obtain it from the network administrator. Do not attempt to configure an IP address by guesswork!

Usage: Click the up arrow to add bits to the subnet mask. Click the down arrow to take away bits from the subnet mask. The mask and the number of bits in the mask are shown to the right of the arrows.

Dependencies: Keep this additional information in mind:

• The value of the Subnet Mask setting must match the Subnet Mask setting expected by the device to which the Pipeline connects.

• If you do not know the right subnet mask to enter, you must obtain it from the network administrator. Do not attempt to configure the subnet mask by guesswork!

The address specified with the IP Address setting is used for authentication. In all other respects, the two IP addresses are treated equally.

Specifying a second address doubles the number of entries in the Pipeline routing table. The Pipeline advertises a route from 2nd Address to IP Address and a route from IP Address to 2nd Address.

One use of 2nd Address is to advertise routes that would not otherwise be advertised. For example, suppose both the Pipeline and Router2 have a route to the network 200.0.2.0. Both are on the same subnet. The device with the lower hop count to the destination network sends all the traffic destined for that network. Now, suppose the value of 2nd Address is 200.0.2.9 and the value of Subnet Mask for this address is 28, and the value of 2nd Address for Router2 on the same subnet is 200.0.2.10 and the value of Subnet Mask for this address is also 28. The Pipeline assumes that all subnets in the 200.0.2.0 network have the same subnet mask (28). In addition, the Pipeline has an address for a router at 200.0.2.129 (whose Subnet Mask value is 28) and Router2 has an address for a router at 200.0.2.65 (whose Subnet Mask value is also 28). The Pipeline routes traffic only to the 200.0.2.129/28 subnet and Router2 routes traffic only to the 200.0.2.65/28 subnet. The traffic to the 200.0.2.0 network is thereby shared.

Using the 2nd Address setting also provides an easy way to change the IP address of the Pipeline. When all routers know the Pipeline by both its IP Address value and its 2nd Address value, you can safely turn off 2nd Address and put the new address in IP Address.

Usage: Enter the second IP address for the Pipeline.

The address consists of four numbers between 0 and 255, separated by periods. The IP address must be a valid IP address on the remote Ethernet network.

Example: 20.2.1.1

Dependencies: Keep this additional information in mind:

• The value of the 2nd Address setting must match the value expected by the device to which the Pipeline connects.

• If you do not know the right IP address to enter, you must obtain it from the network administrator. Do not attempt to configure an IP address by guesswork!

• You cannot use 2nd Address to force interface-based routing; it cannot be used as a second WAN address.

Usage: Click the up arrow to add bits to the subnet mask. Click the down arrow to take away bits from the subnet mask. The mask and the number of bits in the mask are shown to the right of the arrows.

Dependencies: Keep this additional information in mind:

• The value of the Subnet Mask setting must match the Subnet Mask setting expected by the device to which the Pipeline connects.

• If you do not know the right subnet mask to enter, you must obtain it from the network administrator. Do not attempt to configure the subnet mask by guesswork!

Domain Name Service (DNS) is a TCP/IP service that enables you to specify a symbolic name instead of an IP address. A symbolic name consists of a username and a domain name in the format username@domainname. The username corresponds to the host number in the IP address. The domainname corresponds to the network number in the IP address. A symbolic name might be steve@abc.com or joanne@xyz.edu.

DNS maintains a database of network numbers and corresponding domain names on a domain name server. When you use a symbolic name, DNS translates the domain name into an IP address, and sends it over the network. When the Internet service provider receives the message, it uses its own database to look up the username corresponding to the host number.

Usage: Enter the domain name for your Pipeline.

Example: berkeley.cpusa.gov

Domain Name Service (DNS) is a TCP/IP service that enables you to specify a symbolic name instead of an IP address. A symbolic name consists of a username and a domain name in the format username@domainname. The username corresponds to the host number in the IP address. The domainname corresponds to the network number in the IP address. A symbolic name might be steve@abc.com or joanne@xyz.edu.

DNS maintains a database of network numbers and corresponding domain names on a domain name server. When you use a symbolic name, DNS translates the domain name into an IP address, and sends it over the network. When the Internet service provider receives the message, it uses its own database to look up the username corresponding to the host number.

Usage: Enter the IP address of the primary domain name server.

The address consists of four numbers between 0 and 255, separated by periods. The default value is 0.0.0.0. Accept this default if you do not have a domain name server.

Example: 200.207.23.1

Domain Name Service (DNS) is a TCP/IP service that enables you to specify a symbolic name instead of an IP address. A symbolic name consists of a username and a domain name in the format username@domainname. The username corresponds to the host number in the IP address. The domainname corresponds to the network number in the IP address. A symbolic name might be steve@abc.com or joanne@xyz.edu.

DNS maintains a database of network numbers and corresponding domain names on a domain name server. When you use a symbolic name, DNS translates the domain name into an IP address, and sends it over the network. When the Internet service provider receives the message, it uses its own database to look up the username corresponding to the host number.

Usage: Enter the IP address of the secondary domain name server.

The address consists of four numbers between 0 and 255, separated by periods. The default value is 0.0.0.0. Accept this default if you do not have a secondary domain name server.

Example: 200.207.23.1

Dependencies: Keep this additional information in mind:

• The Secondary DNS setting applies only to Telnet connections running under the Pipeline terminal server interface.

  A terminal server is a computing device to which a terminal can connect over a LAN or WAN link. The Pipeline supports all the common capabilities of standard terminal servers, including Telnet, Domain Name Services (DNS), login and password control, call detail reporting, and authentication services.

  Telnet is a protocol used to link two computers in order to provide a terminal with a connection to the remote device. The remote device is known as the Telnet host. When you start a Telnet session, you connect to the Telnet host and log in. The connection enables you to work with the remote machine as though you were at a terminal connected to it.

DNS can return multiple addresses for a hostname in response to a DNS query. Unfortunately, DNS has no information about the availability of those hosts. Users typically attempt to access the first address in the list. If that host is unavailable, the connection fails and the user must initiate a new DNS query or Telnet attempt. If the login attempt occurs automatically as part of Immediate Telnet, the Pipeline tears down the physical connection when the initial connection attempt fails.

The DNS List Attempt feature helps the Pipeline avoid tearing down physical links by enabling the user to try one entry in the DNS list of hosts when logging in through Telnet from the terminal server; if that connection fails, the user can try each succeeding entry.

Usage: Check the checkbox to enable the DNS List Attempt feature.

Note: This setting affects only RIP version 1.

Usage: Choose one of the following:

• Poison Reverse
  With the poison reverse policy, the Pipeline propagates routes back to the subnet from which they were received, but with a metric of 16.

• Split Horizon
  With the split horizon RIP policy, the Pipeline does not propagate routes back to the subnet from which they were received.

Note: RIP Summary only applies to RIP version 1.

Summarizing means that when the Pipeline has a route to a subnet, it advertises a route to all the subnets in a network of the same class. For example, if the Pipeline has a routing table entry to 200.5.8.13/28, it advertises a route to 200.5.8.0, because 200.5.8.13/28 is part of a class C network. When the Pipeline does not summarize information, it advertises each route in its routing table "as-is"; in our example, the Pipeline advertises a route only to 200.5.8.13.

RIP (Routing Information Protocol) is defined without consideration for subnetting; entries in a RIP packet do not include a subnet mask. Therefore, the recipient of such updates must know or assume information about subnet masks. To work around this standard RIP behavior, the Pipeline includes the RIP Summary setting. You can set this setting to specify that the Pipeline modify RIP to advertise implied subnet information.

• Yes
  With this setting the Pipeline summarizes subnet information when advertising routes outside its own network, but does not summarize subnet information when advertising routes inside its own network.

  For example, suppose the Pipeline has an IP address of 200.8.143.5/28 and advertises across the WAN to a router that has the address 200.8.143.31/28. Even though the Pipeline and the recipient are on different subnets, they are on the same network; therefore, no summarization takes place. The routes are sent as-is.

• No
  With this setting the Pipeline does not summarize subnet information when advertising routes. The recipient must know the subnet mask to apply to each route.

• The RIP Summary setting applies only to RIP version 1 and has no affect on RIP version 2 advertisements.

• RIP Summary does not affect host routes.

  For example, if the Pipeline has a routing table entry to 200.8.143.5/32, this route is advertised as 200.8.143.5, regardless of whether routes are summarized.

Usage: Check the box to make the Pipeline ignore RIP updates to the default route.

Usage: Choose one of the following:

• Off
  This setting disables proxy mode.

• Active
  This setting specifies that the Pipeline responds to an ARP request only if a connection to the remote site is up, regardless of whether a Connection Profile exists for the link.

• Inactive
  This setting specifies that the Pipeline responds to an ARP request only for a remote IP address specified in a Connection Profile, and only if there is no connection to the remote site.

• Always
  This setting specifies that the Pipeline responds to an ARP request regardless of whether a connection to the remote site is up.

• The ARP Proxy Mode setting is dimmed if the Pipeline does not perform IP routing.

• Enabling proxy mode may prevent the Pipeline from placing calls simply for address lookups.

The Pipeline should not accept ICMP Redirect messages if it maintains a routing table, because counterfeit ICMP Redirect messages pose a potential security threat.

The Pipeline should accept ICMP Redirects only when it has a single default route to another device.

Usage: Check the box to cause the Pipeline to accept Internet ICMP Redirect messages.

IPX packets can appear in more than one Ethernet frame type on an Ethernet segment. If your Pipeline routes IPX, it can recognize only a single IPX frame type. The Pipeline does not route other IPX frame types, and may attempt to bridge them. In addition, the Pipeline can only route and perform watchdog spoofing for the IPX frame type specified by Frame Type.

Usage: Choose one of the following:

• Ethernet II
  This setting specifies the Ethernet II frame type.

  It indicates that IPX clients and servers on the local Ethernet network follow the Ethernet II protocol for the MAC header.

• Ethernet 802.2
  This setting specifies the 802.2 frame type.

  It indicates that the IPX clients and servers on the local Ethernet cable follow the IEEE 802.2 protocol for the MAC header. The framer contains the LLC (Logical Link Control) header in addition to the MAC (Media Access Control) header.

  For NetWare 3.12 or later, select Ethernet 802.2.

  802.2 is the default.

• Ethernet 802.3
  This setting specifies the 802.3 frame type.

  It indicates that IPX clients and servers on the local Ethernet cable follow the IEEE 802.3 protocol for the MAC header, also called Raw 802.3. The frame does not contain the LLC (Logical Link Control) header in addition to the MAC (Media Access Control) header.

  For NetWare 3.11 or earlier, select 802.3.

• Ethernet 802.2 SNAP
  This setting specifies the SNAP frame type.

  It indicates that the IPX clients and servers on the local Ethernet network follow the SNAP (SubNetwork Access Protocol) for the MAC header. This specification includes the IEEE 802.3 protocol format plus additional information in the MAC header.

• None
  This setting disables IPX routing and other IPX-specific features.

  If you choose None, the Pipeline can bridge IPX, but without watchdog spoofing or the automatic RIP (Routing Information Protocol) and SAP (Service Advertising Protocol) data filters described in Discard RIP, SAP.

• Select 802.3 if the Frame setting is Ethernet_802.3.

• Select 802.2 if the Frame setting is Ethernet_802.2.

• Select SNAP if the Frame setting is Ethernet_SNAP.

• Select Enet II if the Frame setting is Ethernet_II.

The Pipeline assigns an address to a workstation when it connects to the Pipeline; it derives the address from the network number.

Usage: Enter an IPX network number using an 8-digit (4-byte) hexadecimal value. The default is 00000000. The number you specify must be unique within your wide-area IPX network, and must match the configuration of other routers on the local Ethernet network.

When you accept the default setting of 00000000, the Pipeline learns its IPX network number from other routers on the Ethernet network. If you enter a value other than zero, the Pipeline becomes the "seeding" router and sets its IPX network number for the other routers on the Ethernet network

Example: DE040600

Dependencies: The LAN Network Number setting does not apply if the Pipeline is not set up for IPX routing (Route IPX setting is unchecked).

When you enter a value for WAN Network Number, the Pipeline advertises a route to this network.

Usage: Enter an Ethernet network number using an 8-digit (4-byte) hexadecimal value. The default is 00000000.

The number you specify must be unique within your wide area IPX network, and must match the configuration of other routers on the local Ethernet network.

Dependencies: Keep this additional information in mind:

• The dial-in Netware client must accept the network number set by WAN Network Number, although it can provide its own node number or accept a node number provided by the Pipeline.

• If the Frame Type setting is None or the Enable IPX setting is unchecked, the WAN Network Number setting is dimmed.

When a Pipeline is used to connect NetWare clients to a very large IPX network, the SAP table created by the Pipeline can become very large and unmanageable. As an alternative, the Pipeline operating in proxy mode discards all SAP broadcasts seen on the network and resolves SAP queries from NetWare clients as it receives them, by forwarding the queries over the WAN link.

SAP proxy mode is recommended when only NetWare clients (not servers) are on the Ethernet side of Pipeline.

If the Pipeline running in SAP proxy mode has NetWare servers on its Ethernet, it stores the relevant SAP entries for those servers and advertises them across the WAN interface as a normal SAP broadcast.

Usage: Choose one of the following

• Yes
  This enables IPX SAP Proxy mode.

• No
  This disables IPX SAP Proxy mode.

• This setting is dimmed if the Frame Type setting is None.

• For the Pipeline to use IPX SAP Proxy mode, you must use the IPX SAP Proxy Network # setting to specify the remote IPX network number and configure a static IPX route to that network.

Usage: Enter an 8-digit hexadecimal IPX network number.

Example: A1236B59

Dependencies: This setting is dimmed if the IPX SAP Proxy setting is No.