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 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: Click this to open the Pipeline Monitor.

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!

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:

• If there is no authenticated dial-up session and the Pipeline receives a DHCP Discover packet, it responds with a DHCP Offer packet containing the configured IP address, netmask, and renewal time. This is quickly verified by an exchange between the client and the Pipeline.

• The renewal time is limited to a few seconds to ensure that the computer gets its real address from the remote DHCP server as soon as possible.

• The APP Server utility runs using only broadcast addresses (see the discussion on the APP Server Utility and DHCP Spoofing in the Pipeline 75 User's Guide), so that the Pipeline does not need a real IP address and the temporary "spoofed" address is not relied upon.

• As soon as an authenticated dial-up link exists, the Pipeline refused to renew the spoofed address, forcing the computer to get its real address from the remote DHCP server.

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:

• The Internet Protocol (IP) address for the computer.

  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.

• The subnet mask for the computer.

  This is the same as the subnet mask for the MAX.

• The IP address of the default gateway for the connecting to remote networks.

  This is the IP address of the MAX.

• The IP address of a domain name server (DNS server) that the computer can use.

  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.

The address consists of four numbers between 0 and 255, separated by periods.

Dependencies: 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:

• 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!

Usage: If checked, the Pipeline advertises itself as the default router in DHCP replies. This is unchecked by default.

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.

The default is 10.

Dependencies: For DHCP spoofing to work, you must also provide values for the Enable, Spoof Address, and Subnet Mask settings.