Release Notes for 3.1.1 --> 3.1.2 This document describes bug fixes and enhancements made to the PortMaster operating system between release 3.1.1 and 3.1.2. This release note and earlier ones are available on ftp://ftp.livingston.com/pub/livingston. Enhancements 1. Added immediate disconnect when RADIUS sends a Reject with a zero length user message. No message will generate "Invalid Login" and a non-zero length message will display only the message. This is useful when the RADIUS server wishes to disconnect an un-authorized user without allowing for multiple login retries. 2. Support for 4 or 16 megabytes of memory has been added. The PortMaster will auto-detect the physical installed memory. 70ns SIMMs are required, and there must be 4 SIMMs, all of them either 256K, 1MB, or 4MB. Mixing SIMMs is not supported. Bug Fixes 1. When using Frame Relay on a sync port FECN, BECN, and DE bits are removed from DLCI headers of Inverse ARP requests to properly glean ARP table entries from Frame Relay switches which assert these bits. 2. Dial-in PPP users who refuse all forms of authentication are shutdown immediately after completing LCP negotiation instead of waiting for Carrier to drop. 3. Partially open PPP sessions are now properly shutdown. This bug was introduced in Release 3.1.1. Sessions which completed the LCP and authentication phases and then did not complete the IP or IPX negotation were not being properly shutdown. The most common effect was that assigned IP addresses were not being released. This resulted in using out of range IP addresses in future address assignments. ________________________________________________________________________ Release Notes for 3.1 --> 3.1.1 This document describes bug fixes and enhancements made to the PortMaster operating system between release 3.1 and 3.1.1. This release note and earlier ones are available on ftp://ftp.livingston.com/pub/livingston. Enhancements 1. The administration prompt has now been enhanced to display the "System Name" followed by a ">" instead of "Command>" on PortMasters which have had their System Name set (with "set sysname"). 2. Support was added for extended length messages coming from the RADIUS server. Messages can now be up to 2000 bytes long. This is accomplished by concatenating multiple "Port-Message" fields together. 3. Scheduler latency improvements. The speed in which certain events are processed has been increased. This was accomplished by decreasing the rate at which certain non-critical events were being processed. The effect being that high priority events are processed more quickly. 4. The Annex-D version of LMI has been added for use with Frame Relay. The command "set annex_d Interval" where "Interval" is the number of seconds between LMI requests will enable this feature. Setting "Interval" to zero (0) or enabling the older LMI will disable Annex-D. 5. "show netconns" now truncates the hostname to fewer characters to assure that the TCP or UDP port number is not truncated. 6. Small packet from ethernet performance enhancement. Small packets (less that 128 bytes) are now loaded directly into internal NetBufs from the Ethernet controller. This eliminates a duplicate copy, decreasing latency and enhancing throughput. 7. "show arp frmW1" on PM2R and PM2eR now shows DLCI as well as Q.922 address. (Actually, added in 3.1) 8. RADIUS User-Name increased from 31 characters to 63. Bug Fixes 1. The PortMaster "PANIC" during a save command has been fixed. After upgrading to 3.1 approximately 1% of the installed systems would experience a system PANIC when trying to save data to the FLASH file system. The bug which caused this has been removed. 2. Users being prompted for a host, which are being authenticated by RADIUS will no longer be given the "Missing password entry" message. 3. Inverse ARP compatibility. Inverse ARP in earlier releases was not compatible with other vendors' implementations. This has been fixed. In addition, a feature to maintain backward compatibility was added. 4. Sync ports will now properly restart after a loss of carrier or a port reset. This only affects the PM2eR series. In some cases, after resetting the sync port, the only way to get the port to become operational was to reboot. This has been fixed. 5. A memory leak in the IPX SAP subsystem has been removed. This leak occurred in networks with unstable, rapidly changing SAP tables.