OpenROUTE 3.0 [R1]
Release Notes

These release notes are for OpenROUTE 3.0 [R1] software. They cover the following topics:

New Software Functionality

Corrected Problems

Known Deficiencies, Limitations, and/or Clarifications

1.0 New Software Functionality

The following table identifies the new functionality in OpenROUTE 3.0 [R1].

Table 1 OpenROUTE 3.0 [R1] Functionality
Feature	Description
Priority forwarding	Allows you to tag IP packets using IP filters and then prioritize tagged packets using Bandwidth Reservation.
Serial Interface Dialer (DIAL)	Handles the process of placing and receiving telephone calls. DIAL supports asynchronous and synchronous communication, including synchronous V.25 bis.
Frame Relay enhancements	Supports virtual circuits, LAN emulation, and Frame Relay Manager.
Frame Relay (FR) over HSSI	Allows you to run FR over the High Speed Serial Interface (HSSI) card.
HTTP authentication	Authenticates users to access services behind the firewall using a Web browser, such as Netscape.
ISDN BRI enhancements	Provides Data Over Speech Bearer Service (DOSBS) and Frame Relay over ISDN.
NetWare Link Services Protocol (NLSP)	Provides link-state routing protocol for NetWare IPX networks.
New software architecture	Allows you to create protocol stacks and device pools.
Routing Information Protocol (RIP) V2	Provides enhancements to RIP V1.
Triggered RIP	Exchanges routing updates only when there is a change in routing information.
Interface Utilization Measurement	Provides utilization measurements for all interfaces.
PPP Data Compression enhancement	Provides additional PPP data compression capability.
D Channel Call-back	Lets you set up Call-back on an ISDN interface so that the local router does not answer the incoming call, and the remote router does not incur the expense of placing the call.
Network Address Translation (NAT)	Lets a router represent an entire LAN to the Internet as a single, global IP address. The Internet sees all traffic from the local network as originating from the global IP address. Likewise, all traffic coming into the local network from the Internet is addressed to the global IP address. This allows your ISP to assign one IP address to your LAN, instead of allocating a block of IP addresses, one for each computer on the network. This implementation of NAT is compliant with RFC 1631, The IP Network Address Translator (NAT).

2.0 Corrected Problems

The following problems have been corrected since the OpenROUTE 2.3a software release.

Previously, when running IPX, AppleTalk, or Bridging over a PPP link, you had to either enable or disable these protocols on both ends of the link. Otherwise, the router on which the protocol was enabled ran out of buffer memory and crashed.
WAN Reroute was not supported in an ISDN to ISDN configuration or in an ISDN to Ethernet configuration. OpenROUTE now supports these configurations.
When Bandwidth Reservation System (BRS) processes a bridged PPP packet, it strips a fixed-length four-byte PPP header from the packet before determining the data type (NetBIOS, SNMP, etc.). BRS uses the data type to determine the correct BRS class. Previously, the PPP header was not a fixed length, and could be from 1 to 4 bytes long. Now the PPP header is always 4 bytes long.
Previously, when you added a user to the OpenROUTE configuration using the command line interface, the software allowed you to enter Challenge as the type of authentication even if you were not running a GTSecure version of software. Only users who have the GTSecure Login utility can respond to a challenge. If you do not have the utility, adding only one user with an authentication type of Challenge can prevent you from accessing the router configuration.

3.0 Known Deficiencies, Limitations, and/or Clarifications

This section explains known deficiencies in OpenROUTE 3.0 [R1] and indicates limitations with the software.

3.1 General

In previous releases of OpenROUTE, routers that supported dial circuits used a proprietary protocol, known as the Line ID protocol, to identify the calling router. OpenROUTE 3.0 [R1] does not support the proprietary Line ID protocol. OpenROUTE 3.0 [R1] uses PAP, CHAP, and caller ID to identify callers.
Increase table sizes with caution. OpenROUTE Networks advises that you need an understanding of the routing environment and available memory on the router to do so.
OpenROUTE Networks recommends that the maximum number of dial interfaces you configure on a GT 60 or 70 is eight. Adding more than the recommended dial interfaces causes the router to exhaust available memory and crash during initialization. If this happens, you have to clear your configuration before reloading, unless you saved a configuration with no more than the maximum number of dial interfaces.
You should leave the timeout parameter of the add dump-entry command at its default value of 10. Large values (such as 120 seconds) sometimes prevent crash dumps from completing.
GT 60 Series, GT 70 Series, and GTS 100 routers do not have a time of day clock chip with battery backup. For time to be meaningful, you have to get the time from a nearby host. The time commands at the Config> prompt allow for this operation. Enter time set at restarts or set up the time configuration to poll a nearby host.

3.2 WAN Interfaces - General

Under extremely heavy traffic over a WAN interface, routing packets for some protocols may be dropped. This can destabilize routing protocols, causing sporadic reachability. This is inherent in the nature of these routing protocols. To avoid this condition, enable Bandwidth Reservation on both ends of the WAN connection.

3.3 ISDN

If the ISDN switch providing the connection supports Caller-ID authentication, set the Circuit Manager Access List to the name of the remote router(s), you configured in the ISDN Address List.
The GT 70 Series Quick Config does not ask for directory numbers for the INS64 switch variant because INS64 does not require them. Therefore, if the INS64 switch needs subaddressing, you must enter the ISDN configuration and explicitly set the directory numbers. For example:
```
Config>network 1
Circuit Configuration
Circuit Config <NET-1> bri
Basic Rate ISDN user configuration
BRI Config <NET-1> set dn0
Enter DN0 (Directory-Number-0) []? 54
```
Note: The directory number 0 (DN0) only has a subaddress component which, in this example, is 54.
GTS 205 routers do not support ISDN configuration using Quick Config. You must enter commands at the command line to set up ISDN on a GTS 205.

3.4 PPP

OpenROUTE 3.0 [R1] supports PPP PAP and CHAP authentication. If the OpenROUTE Networks router is enabled to authenticate another router using PAP and CHAP, OpenROUTE requests CHAP first and then allows the remote router to use PAP if it does not support CHAP. OpenROUTE cannot fall back from CHAP to PAP when another router is the authenticator because, by PPP specification, if a router supports CHAP, and the other router asks for CHAP, the first router must use CHAP.
This may cause confusion if you configure a PAP password on the OpenROUTE router and then enable the other router to authenticate using PAP and CHAP. When the other router asks for CHAP, OpenROUTE complies, but PPP authentication fails because OpenROUTE does not have a CHAP secret configured.
If PAP authentication is required, then the other router (of any brand) must only request PAP. OpenROUTE complies and returns the PAP password that you configured.
A remote router calling into a local router running OpenROUTE 2.3 or higher is not allowed to request PAP from the local router. There is a potential security risk where PAP passwords can be stolen. This introduces a possible incompatibility with OpenROUTE Networks routers prior to OpenROUTE 2.3 that have PAP enabled and other vendor's routers with PAP enabled. Routers running OpenROUTE 3.0 refuse PAP requests because only the router answering the call can request PAP, not the router placing the call. Since the PAP request is refused, the remote router ends the call and thus the link never comes up. The solution is to disable PAP until you have upgraded all routers to OpenROUTE 2.3 or higher. You should use CHAP during the transition. because CHAP is more secure and it is not susceptible to "password stealing." Both ends of a PPP link can request CHAP.
PPP Call-back, which initiates a call-back to a caller without answering the incoming call, only works on the first call received from the caller. If the calling router calls a second time after one call is already established, the receiving router answers the second call momentarily, and then drops the call. Then, the receiving router makes a second call-back. To work around this problem, configure the remote router (that is, the router making the call) to call only once.
If you need Multilink PPP (MP), configure the router receiving the call to bring up the second call either by enabling Bandwidth-on-Demand or by setting the MP initial-bundle-size to two.
OpenROUTE software has sophisticated call collision logic within Multilink PPP (MP) that normally assembles a multilink bundle of two ISDN B channels even when two OpenROUTE routers call each other simultaneously. However, that software requires each router to know the identity of the other router. Therefore, when two routers are both enabled to place outbound calls to each other, you must have caller ID provisioned on your ISDN switch or have PPP PAP or CHAP enabled on the router, so the two routers can correctly identify each other. Otherwise, one of the two calls is refused and call retries begin. This can cause some "thrashing" as call collisions continue to occur while the second B channel is brought up.
GTAM routers do not negotiate CHAP properly. GTAM routers do negotiate PAP properly.

3.5 RADIUS Authentication

The form that the OpenROUTE software presents to the user who is authenticating using HTTP allows the user to enter up to 32 characters. However, when the router sends the authentication request to the RADIUS server, the router sends only the first 15 characters that the user entered.
When a user authenticates using HTTP authentication, the OpenROUTE software does not generate RADIUS ELS messages to show the authentication activity.
GTAM routers do not support RADIUS authentication.

3.6 X.25

When you run IPX WAN over X.25 with the packet size set to 512K, the window size set to the default of 2, and the speed set to 9600 or 19200 bps, the link fails NLSP negotiation. The link comes up using RIP only. To work around this problem, set the packet size and window size on the router in the X.25 National Personality configuration and on each port on the X.25 switch to the same value. A packet size of 512K and a window size of 4 works with speeds of 9600 and 19200 bps. A packet size of 256 and a window size of 6 also works with the speed set to 9600 bps.

3.7 Upgrading to OpenROUTE 3.0 [R1]

OpenROUTE 3.0 [R1] supports two types of Frame Relay interfaces, Frame Relay LAN Emulation (FRLANE) and Frame Relay Virtual Circuit (FRVC). If you are using Frame Relay and upgrade to OpenROUTE 3.0 [R1], the software converts existing Frame Relay interfaces to Frame Relay LAN Emulation (FRLANE) interfaces. For more information, see the OpenROUTE 3.0 [R1] LAN/WAN Interface Guide, available on the OpenROUTE Networks Web site at www.openroute.com.
If you are using Multilink PPP (MP) and are upgrading a GT 70 Series router to OpenROUTE 3.0 [R1], note that the default for MP has changed from disabled to enabled. Therefore, if you previously used the MP default settings, MP changes from disabled to enabled when you upgrade to OpenROUTE 3.0 [R1].
OpenROUTE 3.0 [R1] does not support Proteon Serial Line (PSL). When you upgrade a router that has PSL interfaces, the software converts PSL links to PPP links. In this case, since the router at the other end of the link is running PSL, your WAN link will go down. OpenROUTE Networks recommends that you reconfigure your WAN links to run PPP before you upgrade to OpenROUTE 3.0 [R1].

3.8 GT 70 Series

The console port on GT 70 Series routers does not support autobaud. The baud rate defaults to 9600, but you can change it using the set baudrate configuration command.
When the GT 70 Series router is booting, the LAN and the OK indicator lights both blink. Only the OK indicator light should blink.

3.9 GTAM

GTAM routers do not negotiate CHAP properly. GTAM routers do negotiate PAP properly.
GTAM routers do not support RADIUS authentication.

3.10 Setup Utility

The Setup Utility is not yet available for OpenROUTE 3.0 software.

docs@openroute.com

Copyright © 1997, OpenROUTE Networks, Inc. All rights reserved. OpenROUTE 3.0