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 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.
Update
Description: Sends configuration settings to the Pipeline.
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.
Save As
Description: Saves configuration settings in a file.
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.
Open Monitor
Description: Opens the Pipeline Monitor, a program for monitoring the status of the Pipeline unit as well as making and disconnecting ISDN connections manually. You can also use it to view the current status of the ISDN line as well as events that occur during Pipeline operation. For more information about the Pipeline Monitor, see Using the Pipeline Monitor.
Usage: Click this to open the Pipeline Monitor.
Usage: Choose one of the following:
This displays Internet Protocol (IP) settings. These settings are described in the IP settings section.
This displays IPX settings for Novell NetWare networks. These settings are described in the IPX settings section.
This displays settings for AppleTalk networks. These settings are described in the AppleTalk settings section.
Usage: Check the box to enable bridging of protocols that are not routed.
Dependencies: Keep this additional information in mind:
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
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 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.
Example:
20.2.1.1
Dependencies: Keep this additional information in mind:
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:
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
Usage: Enter a secondary domain name. The name can contain up to 63 characters.
Example: xyz.com
Primary DNS
Description:
This setting specifies the IP address of the primary domain name server. 200.207.23.1
Secondary DNS
Description:
This setting specifies the IP address of the secondary domain name server.
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:
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.
Client DNS configurations define DNS server addresses that will be presented to WAN connections during IPCP negotiation. They provide a way to protect your local DNS information from WAN users. Client DNS has two levels: a global configuration that applies to all PPP connections, and a connection-specific configuration that applies to that connection only. The global client addresses are used only if none are specified in the Connection profile.
This setting acts as a flag to enable the MAX to present the local DNS servers to the WAN connection when all client DNS servers are not defined or available.
Usage: If checked, clients can use the local DNS servers. This is checked by default.
Usage: Enter the IP address of a DNS server to be used for all connections that do not have a DNS server defined. The default value is 0.0.0.0.
Example: 10.9.8.7/24
Usage: Enter the IP address of a secondary DNS server to be used for all connections that do not have a DNS server defined. The default value is 0.0.0.0.
Example: 10.9.8.7/24
List Attempt
Description: This checkbox controls whether the Domain Name System (DNS) List Attempt feature is enabled.
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.
Usage: Enter a number between 0 and 35. The default value is 6.
When DHCP spoofing is enabled, the Pipeline can act as a DHCP server for one IP address. When card-based security is used, the user must interact with the Pipeline to provide the card-based password. This interaction must occur over IP. However, the user doesn't have an IP address yet at the time when the password must be supplied.
To solve this "which came first" problem, the Pipeline supports DHCP spoofing. DHCP spoofing works like this:
Dependencies: For DHCP spoofing to work, you must also provide values for the Spoof Address, Subnet Mask, and Renewal Time settings.
A Pipeline unit returns the following information in its response to a Plug and Play request:
This address is one greater than the IP address of the MAX. For example, if the IP address of the MAX is 200.200.200.100, the IP address of the computer is 200.200.200.101.
This is the same as the subnet mask for the MAX.
This is the IP address of the MAX.
This is the address of the MAX, which serves as a proxy Domain Name Service (DNS) server. This means that DNS requests are sent to the MAX, which forwards them to the domain name servers, if any, on the remote network, receives the results, and then passes the results to the computer.
Dependencies: If Always Spoof is not checked, the Pipeline responds to only the first Plug and Play request from the computer and ignores later requests. If Always Spoof is checked, the Pipeline responds to later requests from the same computer, but not to requests from other computers.
The address must be a valid address on the local network.
Usage: Enter the IP address.
222.65.212.99Dependencies: For DHCP spoofing to work, you must also provide values for the Enable, Subnet Mask, and Renewal Time settings.
Usage: Enter the number of bits for the subnet mask (a number from 0 to 31). The mask corresponding to this number is shown to the right of the number.
Dependencies: Keep this additional information in mind:
Usage: If checked, the Pipeline advertises itself as the default router in DHCP replies. This is unchecked by default.
Dial If Link Down
Description: The Dial If Link Down setting determines whether the Pipeline dials the first Connection Profile when it receives a request from a DHCP client and the WAN link is down.
Usage: If checked, the Pipeline dials the first Connection Profile if required. This is unchecked by default.
Usage: If checked, the Pipeline responds to multiple DHCP requests from a single host. If unchecked, the Pipeline responds to only the first DHCP request and ignores all subsequent requests. This is unchecked by default.
This value represents the amount of time the address will be assigned to the requesting client. After the specified number of seconds, the client must attempt to secure the IP address again. If an authenticated dial-up session is active, the Pipeline refuses the request, forcing the client to obtain its real IP address from the DHCP server on the remote network.
Usage: Enter a number between 3 and 65535.
60Dependencies: For DHCP spoofing to work, you must also provide values for the Enable, Spoof Address, and Subnet Mask settings.
Usage: Check this to enable NAT routing. This is checked by default.
Dependencies: Keep this additional information in mind:
Usage: Click the button, select a Connection Profile from the list that appears, then click OK.
Dependencies: This setting is disabled if Enable NAT Routing is unchecked.
Multicast settings
Usage: Check this to enable multicast forwarding functionality.
When this is checked, the MAX appears to an Multicast router as a multicast client, which receives IGMP (Internet Group Management Protocol) queries from the router and responds to them using IGMP. To dial-in clients, it appears as a multicast router, which sends IGMP queries and forwards multicast traffic.
It is unchecked by default.
Usage: Click the button, select a Connection Profile from the list that appears, then click OK.
Dependencies: This setting is disabled if Forward Multicast Packets is unchecked.
Note: This setting affects only RIP version 1.
Usage: Choose one of the following:
Note: RIP Summary only applies to RIP version 1.
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.
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.
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.
ARP Proxy Mode
Description: This setting specifies the conditions in which the Pipeline performs a proxy Address Resolution Protocol (ARP) resolution. The Pipeline serves as a proxy when it recognizes the IP address of a remote device in an ARP request and then responds to the ARP request by sending its own MAC address.
Usage: Choose one of the following:
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.
Leave the box unchecked if your network uses a protocol other than IPX, or if your IPX network maintains such large RIP and SAP tables that the Pipeline is spending too much time maintaining them.
Dependencies:
Keep this additional information in mind:
IPX Configuration settings
Enable IPX
Description:
This checkbox specifies whether the Pipeline can perform these functions:
Usage:
Check the box to enable IPX routing functions.
Frame Type
Description:
This setting specifies the Ethernet frame type to use for IPX on the Ethernet interface. If you do not specify an Ethernet frame type, the Pipeline cannot route IPX or perform watchdog spoofing for its IPX clients.
It indicates that IPX clients and servers on the local Ethernet network follow the Ethernet II protocol for the MAC header.
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.
802.2 is the default.
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.
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.
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.
To determine the IPX frame type in use, enter the Config command on a NetWare server, or look at the NET.CFG file on an IPX client. Choose a setting based on this information:
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:
DE040600Dependencies: 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:
FF000003
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
Usage: Enter an 8-digit hexadecimal IPX network number.
Example: A1236B59
Dependencies: This setting is dimmed if the IPX SAP Proxy setting is No.
Usage: If checked, support for AppleTalk routing for this connection is enabled. This is unchecked by default.
Dependencies: Keep this additional information in mind:
Usage: Enter the name of the AppleTalk zone containing the Pipeline.
Dependencies: This setting is available only in the special Pipeline software that supports AppleTalk.
Usage: Choose one of the following:
< Causes the Pipeline unit to ignore AppleTalk packets.
Makes the Pipeline unit a seed router (one that provides the AppleTalk network number range to non-seed routers on the AppleTalk network). If this is chosen, the Network Number Range and AppleTalk Zones settings are enabled.
Makes the Pipeline unit a non-seed router (one that gets the AppleTalk network number range from a seed router).
Usage: Enter the first network number in the AppleTalk network.
Dependencies: Keep this additional information in mind:
Usage: Enter the last network number in the AppleTalk network.
Dependencies: Keep this additional information in mind:
The list can include up to 10 zones, the first of which, the default zone, is required. By default, the entries in the list following the default zone are numbered Zone #1, Zone #2, and so on. If there is a zone name assigned to an entry, it appears in the Zone Name setting when the entry is selected.
Usage: To add zone to the list, select an unused entry in the list (these are numbered Zone #1, Zone #2, and so on) and then enter the name of the zone in the Zone Name field to the right. To replace a zone already in the list, select the entry for the zone and then enter the name of the zone in the Zone Name field to the right.
Dependencies: Keep this additional information in mind:
Usage: To enter the name of a zone to be seeded, select an entry in the AppleTalk Zones list and then type the name of the zone in the Zone Name field. The zone name you type appears in that entry. If there was already a zone name for the selected entry, the new zone name you type replaces the previous zone name.
Dependencies: Keep this additional information in mind: