Note: If you have a Pipeline 25-Fx with the IPX Routing option (for connecting to NetWare networks), see the help file for IPX Routing.
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 several miscellaneous settings. These settings are described in the General settings section.
This displays settings that control security card authentication. These settings are described in the Security Card settings section.
This displays settings that control what appears in the system log. These settings are described in the System Log settings section.
This setting is intended for use when two or more Ascend units on the same network are configured with redundant profiles and routes. It is not necessary to use this feature if you have a single Pipeline unit.
This feature was developed in response to a problem that occurred when two or more Ascend units on the same network were configured with redundant profiles and routes. If one of the redundant Pipeline units lost its dialout lines temporarily, it continued to receive outbound packets that should have been forwarded to the redundant Pipeline.
Usage: Enter whatever.
Causes the Pipeline to always advertise its IP routes. Use this setting unless you have redundant Ascend units or don't use dialout routes.
Always is the default.
Causes the Pipeline to stop advertising ("poison") its IP dialout routes if it temporarily loses the ability to dial out.
Usage: Check the box to enable automatic logout.
Usage:
Specify this setting if data integrity is of the highest concern for your environment, and having redundant checks is important; this setting is also appropriate if your UDP-based servers are located on the remote side of a WAN link that is prone to errors.
This is the default. Use the default if you plan to use the data integrity guarantee of the Ethernet or PPP checksum only.
If you connect an Ethernet transceiver to either connector (such as a transceiver that converts Thick Ethernet to Thin Ethernet), choose the connector to which the transceiver is attached.
Usage: Choose one of the following:
Specifies the 10Base-T (unshielded twisted pair) connector
Specifies the Thick Ethernet (10Base-5) connector
Usage: Check the box to enable security card authentication using an APP Server utility.
Enigma Logic SafeWord AS and Security Dynamics ACE authentication servers are examples of APP servers.
Usage: Enter the IP address of the authentication server.
111.65.212.100Dependencies: 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:
Usage: Enter the UDP port number monitored by the APP server.
35Dependencies: Keep this additional information in mind:
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.
Spoof Address
Description: This setting specifies the IP address that will be assigned to a DHCP client when DHCP spoofing occurs.
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.
Subnet Mask
Description:
This specifies the subnet containing the IP address that will be assigned to a DHCP client when DHCP spoofing occurs.
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:
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.
System Log settings
Log to Host
Description: This checkbox controls whether the Pipeline sends warning, notice, and Call Detail Reporting (CDR) records from system logs to the host specified by the Syslog Host Address setting.
CDR is a feature that provides a database of information about each call, including date, time, duration, called number, calling number, call direction, service type, and associated inverse multiplexing session and port. Because the network carrier bills for bandwidth on an as-used basis, and bills each connection in an inverse multiplexed call independently, you can use CDR to understand and manage bandwidth usage and the cost of each inverse multiplexed session.
Usage: Check the box to send warning, notice, and CDR records to the host specified by the Syslog Host Address setting.
Dependencies: For logging to a host to work, you must also provide values for the Syslog Host Address and Facility Group settings.
Syslog Host Address
Description: This setting specifies the IP address of the host to which the Pipeline sends system logs.
Usage: Enter the IP address of the host to receive system logs.
200.207.23.1Dependencies: Keep this additional information in mind:
System logs sent while the value of Facility Group is the same are grouped together in the host's file system. That is, all system logs sent while Facility Group is Local0 are grouped together, all system logs sent while Facility Group is Local1 are grouped together, and so on.
Usage: Choose one of the following:
Local0 is the default.