MultiNet V5.2 Release Notes April 2007 This document contains a list of new features and bug fixes that have been made since MultiNet V5.1. Revision/Update Information: This document supersedes the MultiNet V5.1-A Release Notes Unpublished - all rights reserved under the copyright laws of the United States No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means electronic, mechanical, magnetic, optical, or otherwise without the prior written permission of: Process Software, LLC 959 Concord Street Framingham, MA 01701-4682 USA Voice: +1 508 879 6994; FAX: +1 508 879 0042 info@process.com Process Software, LLC ("Process") makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, Process Software reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Process Software to notify any person of such revision or changes. o Alpha AXP, AXP, MicroVAX, OpenVMS, VAX, VAX Notes, VMScluster, and VMS are registered trademarks of Hewlett-Packard Corporation. o Kerberos. Copyright © 1989, DES.C and PCBC_ENCRYPT.C Copyright © 1985, 1986, 1987, 1988 by Massachusetts Institute of Technology. Export of this software from the United States of America is assumed to require a specific license from the United States Government. It is the responsibility of any person or organization contemplating export to obtain such a license before exporting. WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. M.I.T. makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. o MultiNet is a registered trademark of Process Software. o Secure Shell (SSH). Copyright © 2000. This License agreement, including the Exhibits (Agreement), effective as of the latter date of execution (Effective Date), is hereby made by and between Data Fellows, Inc., a California corporation, having principal offices at 675 N. First Street, 8th floor, San Jose, CA 95112170 (Data Fellows) and Process ii Software, LLC, having a place of business at 959 Concord Street, Framingham, MA 01701 (OEM). o TCPware is a registered trademark of Process Software. o UNIX is a trademark of UNIX System Laboratories, Inc. o All other trademarks, service marks, registered trademarks, or registered service marks mentioned in this document are the property of their respective holders. o Copyright ©1997, 1998, 1999, 2000 Process Software Corporation. All rights reserved. Printed in USA. o Copyright ©2000, 2001, 2002, 2004 Process Software, LLC. All rights reserved. Printed in USA. o If the examples of URLs, domain names, internet addresses, and web sites we use in this documentation reflect any that actually exist, it is not intentional and should not be considered an endorsement, approval, or recommendation of the actual site, or any products or services located at any such site by Process Software. Any resemblance or duplication is strictly coincidental. iii ________________________________________________________________ Contents ________________________________________________________________ CHAPTER 1 INTRODUCTION 1-1 __________________________________________________________ 1.1 TYPOGRAPHICAL CONVENTIONS 1-1 __________________________________________________________ 1.2 OBTAINING TECHNICAL SUPPORT 1-2 1.2.1 Before Contacting Technical Support 1-3 1.2.2 Sending Electronic Mail 1-4 1.2.3 Calling Technical Support 1-5 1.2.4 Contacting Technical Support by Fax 1-5 __________________________________________________________ 1.3 OBTAINING ONLINE HELP 1-6 __________________________________________________________ 1.4 MULTINET FREQUENTLY ASKED QUESTIONS (FAQS) LIST 1-6 __________________________________________________________ 1.5 ACCESSING THE MULTINET PUBLIC MAILING LIST 1-6 __________________________________________________________ 1.6 PROCESS SOFTWARE WORLD WIDE WEB SERVER 1-7 __________________________________________________________ 1.7 OBTAINING SOFTWARE PATCHES OVER THE INTERNET 1-7 __________________________________________________________ 1.8 DOCUMENTATION COMMENTS 1-9 __________________________________________________________ 1.9 CD-ROM CONTENTS 1-9 1.9.1 Online Documentation 1-10 1.9.1.1 PDF Format, 1-10 1.9.1.2 Using Acrobat Reader, 1-11 1.9.1.3 Using XPDF, 1-11 __________________________________________________________ 1.10 NOTE CONCERNING KERBEROS V5 1-12 __________________________________________________________ 1.11 NOTE CONCERNING MULTIWARE 1-12 iii Contents __________________________________________________________ 1.12 NOTE CONCERNING SSH 1-13 __________________________________________________________ 1.13 NOTE: CONCERNING SSH SESSIONS 1-13 ________________________________________________________________ CHAPTER 2 CHANGES AND ENHANCEMENTS 2-1 __________________________________________________________ 2.1 MULTINET V5.2 INSTALLATION NOTE 2-1 __________________________________________________________ 2.2 BG PERFORMANCE IMPROVEMENTS 2-1 __________________________________________________________ 2.3 BIND9 ADDITION 2-1 __________________________________________________________ 2.4 IPSEC UPDATES 2-1 __________________________________________________________ 2.5 IPV6 ADDITIONS 2-2 __________________________________________________________ 2.6 NTP UPDATE 2-2 __________________________________________________________ 2.7 SERVICES 2-2 __________________________________________________________ 2.8 SSH UPDATES 2-2 __________________________________________________________ 2.9 TELNET SERVER (NTY) PERFORMANCE IMPROVEMENTS 2-3 __________________________________________________________ 2.10 FIXED PROBLEMS 2-3 2.10.1 Bootp 2-3 2.10.2 DHCP 2-3 2.10.3 DNS 2-3 2.10.4 Documentation 2-3 2.10.5 FTP 2-4 2.10.6 IMAP 2-4 2.10.7 Kernel 2-4 2.10.8 Master Server 2-8 2.10.9 Named 2-8 2.10.10 NFS 2-8 iv Contents 2.10.11 NTP 2-8 2.10.12 Printing 2-8 2.10.13 RPC 2-9 2.10.14 R Services 2-9 2.10.15 SFTP/SCP2 2-9 2.10.16 SMTP 2-12 2.10.17 SNMP 2-12 2.10.18 Socket Library 2-12 2.10.19 SSH 2-13 2.10.20 Telnet 2-13 2.10.21 TOPS Library 2-14 2.10.22 XDM 2-14 ________________________________________________________________ CHAPTER 3 DOCUMENTATION UPDATES 3-1 __________________________________________________________ 3.1 MULTINET V5.2 3-1 __________________________________________________________ 3.2 CORRECTIONS TO THE MULTINET V5.2 DOCUMENTATION 3-1 ________________________________________________________________ CHAPTER 4 KNOWN BUGS/ISSUES 4-1 ________________________________________________________________ TABLES 1-1 Typographical Conventions 1-1 1-2 System Information 1-4 v _______________________________________________________ 1 Introduction These Release Notes describe the changes and enhancements made to the MultiNet product in version 5.2. This chapter describes conventions used in the MultiNet documentation set and the various methods to contact and receive technical support. o For information about product changes and enhancements in the MultiNet V5.2 MultiNet Consolidated Distribution, refer to Chapter 2 of these Release Notes. o For information about changes to the documentation set, refer to Chapter 3 of these Release Notes. __________________________________________________________ 1.1 Typographical Conventions Examples in these Release Notes use the following conventions: ________________________________________________________________ Table 1-1 Typographical Conventions _______________________________________________________ Convention_______Example__________Meaning______________ Angle brackets Represents a key on your keyboard. Angle brackets Indicates that you with a slash hold down the key labeled or while simultaneously pressing another key; in this example, the A key. 1-1 Introduction Typographical Conventions ________________________________________________________________ Table 1-1 (Cont.) Typographical Conventions _______________________________________________________ Convention_______Example__________Meaning______________ Square brackets [FULL] Indicates optional choices; you can enter none of the choices, or as many as you like. When shown as part of an example, square brackets are actual characters you should type. Underscore or file_name or Between words in hyphen file-name commands, indicates the item is a single ___________________________________________element._____________ __________________________________________________________ 1.2 Obtaining Technical Support Process Software provides technical support if you have a current Maintenance Service Agreement. If you obtained MultiNet from an authorized distributor or partner, you receive your technical support directly from them. You can contact Technical Support by: o Sending electronic mail (Section 1.2.2) o Calling Technical Support (Section 1.2.3) o Faxing a description of your problem to the Technical Support Group (Section 1.2.4) 1-2 Introduction Obtaining Technical Support _____________________________ 1.2.1 Before Contacting Technical Support Before you call, or send email or a fax: 1 Verify that your Maintenance Service Agreement is current. 2 Read the online Release Notes completely. 3 Have the following information available: o Your name o Your company name o Your email address o Your voice and fax telephone numbers o Your Maintenance Contract Number o OpenVMS architecture o OpenVMS version o MultiNet layered products and versions 4 Have complete information about your configuration, error messages that appeared, and problem specifics. 5 Be prepared to let a development engineer connect to your system, either with TELNET or by dialing in using a modem. Be prepared to give the engineer access to a privileged account to diagnose your problem. You can obtain information about your OpenVMS architecture, OpenVMS version, MultiNet version, and layered products with the MULTINET SHOW /LICENSE command. Execute the following command on a fully loaded system and email the output to support@process.com: $ MULTINET SHOW /LICENSE Process Software MultiNet V5.2 Rev A, VAXstation 4000- 90, OpenVMS VAX V7.1 In this example: The machine or system architecture is VAX. 1-3 Introduction Obtaining Technical Support The OpenVMS version is V7.1. The MultiNet version is V5.2. Use the following table as a template to record the relevant information about your system: ________________________________________________________________ Table 1-2 System Information _______________________________________________________ Your System Required_Information_______________Information_________ Your name Company name Your email address Your voice and fax telephone numbers System architecture VAX or Alpha OpenVMS version _________MultiNet_version_______________________________________ Please provide information about installed MultiNet applications and patch kits, by sending a copy of MULTINET:MULTINET_VERSION.; file. _____________________________ 1.2.2 Sending Electronic Mail For many questions, electronic mail is the preferred communication method. Technical Support via electronic mail is available to customers with a current support contract. Send electronic mail to support@process.com. At the beginning of your mail message, include the information listed in Section 1.2.1. Continue with the description of your situation and problem specifics. Include all relevant information to help your Technical Support Specialist process and track your electronic support request. 1-4 Introduction Obtaining Technical Support Electronic mail is answered within the desired goal of two hours, during our normal business hours, Monday through Friday from 8:30 a.m. to 5:00 p.m., United States Eastern Time. _____________________________ 1.2.3 Calling Technical Support For regular support issues, call 800-394-8700 or 508- 628-5074 for support Monday through Friday from 8:30 a.m. to 7:00 p.m., United States Eastern Time. For our customers in North America with critical problems, an option for support 7 days per week, 24 hours per day is available at an additional charge. Please contact your Account Representative for further details. Before calling, have available the information described in Section 1.2.1. When you call, you will be connected to a Technical Support Specialist. Be prepared to discuss problem specifics with your Technical Support Specialist and to let that person connect to your system. If our Support Specialists are assisting other customers and you are put on hold, please stay on the line. Most calls are answered in less than five minutes. If you cannot wait for a Specialist to take your call, please take advantage of our automatic call logging feature by sending email to support@process.com (see the Section on Sending Electronic Mail). _____________________________ 1.2.4 Contacting Technical Support by Fax You can send transmissions directly to Technical Support at 508-879-0042. Before faxing comments or questions, complete the steps in Section 1.2.1 and include all your system information at the beginning of your fax message. Continue with the description of your situation and problem specifics. Include all relevant information 1-5 Introduction Obtaining Technical Support to help your Technical Support Specialist process and track your fax support request. Faxed questions are answered Monday through Friday from 8:30 a.m. to 7:00 p.m., United States Eastern Time. __________________________________________________________ 1.3 Obtaining Online Help Extensive information about MultiNet is provided in the MultiNet help library. For more information, enter the following command: $ HELP MULTINET __________________________________________________________ 1.4 MultiNet Frequently Asked Questions (FAQs) List You can obtain an updated list of frequently asked questions (FAQs) and answers about MultiNet from the Process Software MultiNet home page located at http://www.process.com/techsupport/multinet_faqs.html. __________________________________________________________ 1.5 Accessing the MultiNet Public Mailing List Process Software maintains two public mailing lists for MultiNet customers: o Info-MultiNet@process.com o MultiNet-Announce@process.com The Info-MultiNet@process.com mailing list is a forum for discussion among MultiNet system managers and programmers. Questions and problems regarding MultiNet can be posted for a response by any of the subscribers. To subscribe to Info-MultiNet, send a mail message with the word SUBSCRIBE in the body to Info- MultiNet-request@process.com. The information exchanged over Info-MultiNet is also available via the USENET newsgroup vmsnet.networks.tcp-ip.multinet. You can retrieve the Info-MultiNet archives by anonymous FTP to ftp.multinet.process.com. The archives are located in the directory [MAIL_ARCHIVES.INFO- MULTINET]. 1-6 Introduction Accessing the MultiNet Public Mailing List You can also find the Info-MultiNet archives on the MultiNet consolidated CD-ROM in the directory: [INFO- MULTINET] The MultiNet-Announce@process.com mailing list is a one-way communication (from Process Software to you) used to post announcements relating to MultiNet (patch releases, product releases, etc.). To subscribe to MultiNet-Announce, send a mail message with the word SUBSCRIBE in the body to MultiNet-Announce- request@process.com. __________________________________________________________ 1.6 Process Software World Wide Web Server Electronic support is provided through the Process Software web site which you can access with any World Wide Web browser; the URL is http://www.process.com (select MultiNet) or use the URL http://www.process.com/techsupport/multinet.html __________________________________________________________ 1.7 Obtaining Software Patches over the Internet Process Software provides software patches in save set and ZIP format on its anonymous FTP server, ftp.multinet.process.com. For the location of software patches, read the .WELCOME file in the top-level anonymous directory. This file refers you to the directories containing software patches. To retrieve a software patch, enter the following commands: $ MULTINET FTP/USERNAME=ANONYMOUS/PASSWORD="emailaddress" - _$ FTP.MULTINET.PROCESS.COM A message welcoming you to the Process Software FTP directory appears next followed by the FTP prompt. Enter the following at the FTP prompt: FTP.MULTINET.PROCESS.COM>CD [.PATCHES.MULTINETxxx] FTP.MULTINET.PROCESS.COM>GET update_filename 1-7 Introduction Obtaining Software Patches over the Internet In these commands: emailaddress is your email address in the standard user@host format xxx is the version of MultiNet you want to transfer update_filename is the name of the file you want to transfer To transfer files from Process Software directly to an OpenVMS system, you can use the GET command without any other FTP commands. However, if you need to transfer a software patch through an intermediate non-OpenVMS system, use BINARY mode to transfer the files to and from that system. In addition, if you are retrieving the software patch in save set format, make sure the save set record size is 2048 bytes when you transfer the file from the intermediate system to your OpenVMS system. o If you use the GET command to download the file size from the intermediate system, use the FTP RECORD- SIZE 2048 command before transferring the file. o If you use the PUT command to upload the file to your OpenVMS system, log into the intermediate system and use the FTP quote site rms recsize 2048 command before transferring the file. Process Software also supplies UNZIP utilities for OpenVMS VAX and Alpha for decompressing ZIP archives in the [PATCHES] directory. To use ZIP format kits, you need a copy of the UNZIP utility. The following example shows how to use UNZIP utility, assuming you have copied the appropriate version of UNZIP.EXE to your current default directory: $ UNZIP := $SYS$DISK:[]UNZIP.EXE $ UNZIP filename.ZIP Use VMSINSTAL to upgrade your MultiNet system with the software patch. 1-8 Introduction Documentation Comments __________________________________________________________ 1.8 Documentation Comments Your comments about the information in these Release Notes can help us improve the documentation. If you have corrections or suggestion for improvement, please let us know. Be as specific as possible about your comments: include the exact title of the document, version, date, and page references as appropriate. You can send your comments by email to techpubs@process.com or mail them to: Process Software 959 Concord Street Framingham, MA 01701-4682 Attention: Marketing Director You can also fax your comments to us at 508-879-0042. Your comments about our documentation are appreciated. __________________________________________________________ 1.9 CD-ROM Contents The directory structure on the CD is as follows: [MULTINET052] MultiNet Kit for VAX and Alpha systems [MULTINET_I64052] MultiNet Kit for Integrity Systems [Documentation] PDF format (.pdf) HTML format (.htm) Release Notes [BIND-DOC] [BIND9-DOC] [XPDF] [XPDF.AXP] for Alpha images [XPDF.VAX] for VAX images [LYNX] [LYNX.AXP] for Alpha images [LYNX.VAX] for VAX images [VAX55-DECC-RTL] 1-9 Introduction CD-ROM Contents _____________________________ 1.9.1 Online Documentation The MultiNet documentation set is available on the product CD in PDF format. The Release Notes are available on the product CD in text format. _____________________________ 1.9.1.1 PDF Format The MultiNet documentation set has the following PDF files: o MULTINET_ADMIN_GUIDE.PDF (Installation and Adminstrator's Guide) o MULTINET_ADMIN_REFERENCE.PDF (Administrator's Reference Guide) o MULTINET_MESSAGES.PDF (Messages, Logicals, & DECnet Apps) o MULTINET_PROGRAMMERS_REFERENCE.PDF (Programmer's Reference) o MULTINET_USER_GUIDE.PDF (User's Guide) The PDF format is readable from a PC, a VAX, or an Alpha system. There is a PDF reader on the CD for each platform. o Use Adobe Acrobat to read the PDF files from a PC. Your PC must have 386 architecture or later to use Adobe Acrobat Reader. You can get Acrobat Reader free from Adobe Systems' Website: www.adobe.com. o Use the XPDF Reader (found in the [XPDF] directory) to read the PDF files from a VAX or Alpha system. The [XPDF.AXP] directory contains the Alpha architecture reader XPDF_AXP.EXE. The [XPDF.VAX] directory contains the VAX architecture reader XPDF_ VAX.EXE. Note The XPDF Reader does not work on a PC. 1-10 Introduction CD-ROM Contents PCs running the Windows or NT operating system cannot read Process Software's CD. You cannot load files from the MultiNet CD directly to a PC. Load them to your VAX or Alpha machine, then transfer them to your PC. We suggest using FTP to transfer these files. The following is an example using MS-DOS: C:> ftp node ftp> binary ftp> mget cd:*.pdf In addition, Process Software has included LYNX, the character-cell Web browser for VMS. It is in the [LYNX] directory. _____________________________ 1.9.1.2 Using Acrobat Reader To read the PDF files using Acrobat Reader: 1 Double click Acrobat Exchange. 2 Choose Open from the File menu. 3 Select the .pdf file you want to open. 4 Use the menu bar at the top of the screen to navigate the document, or click a Table of Contents entry (on the left) to go directly to that information. Note The binocular icon opens search functions. The magnifying glass icon enlarges the text and illustrations. _____________________________ 1.9.1.3 Using XPDF Thanks to Derek B. Noonburg for letting us download his XPDF application. Note You need a three-button mouse to use XPDF. 1-11 Introduction CD-ROM Contents At the DCL prompt from the directory in which XPDF_ VAX.EXE or XPDF_AXP.EXE is stored, do the following: 1 Type RUN XPDF_VAX.EXE or RUN XPDF_AXP.EXE. The XPDF screen appears. 2 Position the arrow on any of the icons (except the ? icon) on the bottom of the screen. 3 Press the right nouse button to display choices. 4 Select OPEN to display the list of PDF files. 5 Select the PDF file you want, and click OPEN to read the file. 6 Use the icons on the bottom of the screen to search for the information you want. To view the online help for XPDF: 1 Position the cursor on the question mark (?) icon. 2 Press the left mouse button to open the online help. __________________________________________________________ 1.10 Note Concerning Kerberos V5 MultiNet now supports Kerberos V5 for SSH and Telnet (Alpha and Integrity only). Kerberos V5 requires Kerberos for HP OpenVMS. VMS V8 systems are distributed with Kerberos V5, and pre-V8 systems (OpenVMS VAX V7.3 and OpenVMS AXP v7.2-3, 7.3-*) can download Kerberos V5 from the HP website. The Kerberos V5 applications can also run with any Kerberos V5 compliant Key Distribution Center (KDC) software. __________________________________________________________ 1.11 Note Concerning MultiWare If you want to continue to use MultiWare with MultiNet, do not install MultiNet V5.2 on your system. MultiWare and all MultiWare-related applications, including management/configuration functionality, have been removed. MultiWare was desupported by TGV prior to 1997. 1-12 Introduction Note Concerning SSH __________________________________________________________ 1.12 Note Concerning SSH You must install the DEC C 6.0 backport library on all OpenVMS VAX v5.5-2 and v6.0 systems prior to using SSH. This is the AACRT060.A file. You can find the ECO on the MultiNet CD in the following directory: VAX55_DECC_ RTL.DIR. __________________________________________________________ 1.13 Note: Concerning SSH Sessions For each active SSH session two(2) channels are used. Please adjust the CHANNELCNT parameter to account for this usage. 1-13 _______________________________________________________ 2 Changes and Enhancements This chapter describes the changes and enhancements made for MultiNet V5.2. __________________________________________________________ 2.1 MultiNet V5.2 Installation Note A new question has been added to the installation asking if the SSH portion of MultiNet should be installed. MultiNet V5.2 installations may only be performed from a random-access device (e.g., disk or CD-ROM). If the MultiNet V5.2 installation is attempted from a sequential-access device (e.g., magtape or TKxx cartridge), the installation will fail. If the distribution savesets have been copied to a sequential- access device (for transporting them, for example), they must be copied to a disk for installation. __________________________________________________________ 2.2 BG performance improvements The read and write QIO paths for the BG driver have been reworked to improve performance. The method in which TCP packets are constructed has been changed to eliminate the need for a buffer copy at transmission time on Alpha and Integrity systems. __________________________________________________________ 2.3 BIND9 Addition BIND9 has replaced BIND8. __________________________________________________________ 2.4 IPSEC updates The RACOON Internet Key Exchange daemon has been added to exchange keys for IPSEC. Layer 3 virtual private network support has been added with the GIF interface. 2-1 Changes and Enhancements IPv6 Additions __________________________________________________________ 2.5 IPv6 Additions IPv6 has been added. BIND9, FTP, NTP, and SSH are capable of using IPv4 and/or IPv6 connections. Additional services will get the ability to use IPv6 in future releases. IPv6 is only supported on the SE, PD, and STF interfaces. The STF (Six-to-Four) interface allows IPv6 traffic to be sent over an IPv4 route to another system with an STF interface. Interfaces are not enabled for IPv6 traffic by default and the configuration will need to be modified to enable it. Note The DHCP Server and DHCP Client only work with IPV4 addresses. __________________________________________________________ 2.6 NTP Update NTP has been updated from NTP 4.1.1 to NTP 4.2. The new DST time changes have also been updated. __________________________________________________________ 2.7 Services The following services have had their socket family changed from AF_INET to AF_INET6 to allow them to be used from both IPv4 and IPv6 FTP, TELNET, DISCARD, ECHO, CHARGEN, DAYTIME __________________________________________________________ 2.8 SSH Updates SSH has been updated to the latest release from WRQ. This updates includes: o A new tool, SSH-CERTTOOL, can be used to generate PKCS#10 and PKCS#12 requests, and to view PKCS#10 and PKCS#12 packages. o The SSH-CERTENROLL2 tool has been renamed to SSH- CMPCLIENT. o The address (IPv4 or IPv6) on which to listen may now be specified as an SSH parameter in CONFIGURE/SERVER. 2-2 Changes and Enhancements SSH Updates o The SSH client may now specify using either IPv4 or IPv6 to make connections. __________________________________________________________ 2.9 Telnet Server (NTY) performance improvements The lock usage for NTY devices has been changed to reduce the number of calls to obtain and release device locks. __________________________________________________________ 2.10__Fixed_Problems_________ 2.10.1 Bootp o Correct an error in BOOTP in setting the ARP information for the client system. [10125] _____________________________ 2.10.2 DHCP o Corrected a bug in the DHCP server where a NULL zone group could cause the server to crash while doing a dynamic updates. [10352] _____________________________ 2.10.3 DNS o Implements Bind 8.3 enchancement which increases nameserver chaining distance from 1 to 3. Solves recursive resolution problem with remote nameservers. [10487] _____________________________ 2.10.4 Documentation o Updated the documentation to reflect additional facility names for syslog. [10219] 2-3 Changes and Enhancements Fixed Problems _____________________________ 2.10.5 FTP o Code that handles the MULTINET_FTP_SERVER_DATA_PORT_ RANGE has been corrected to allow ports greater than 32767. [10373] o The accuracy of the value returned by the SIZE command has been improved. The SIZE command can now be disabled for situations where the client has difficulties because the value returned may be an estimate. If the logical MULTINET_FTP_DISABLE_SIZE is defined to True, Yes, or 1, then the SIZE command will be treated as an unknown command. [10206] o Problems with processing SET HOST/USER=/PASSWORD= in FTP.INIT have been corrected. [10456] _____________________________ 2.10.6 IMAP o Corrected a bug in the IMAP server which caused the timezone offset displayed in INTERNALDATE responses to be "+0000" rather than the correct timezone offset under certain conditions. [10078] _____________________________ 2.10.7 Kernel o Modified a calculation that involves checking the amount of buffer space a socket can use to avoid overflows. This allows values larger than 524287 to be used for the kernel variable SB_MAX and restores the limits that MultiNet V4.4 had. [10481] o The kernel variable ARP_OVERWRITTEN_LOGS is now accessible again. [10451] o Gethostbyname now returns results of gethostbyaddr when given an IP address. [10433] o Errors in processing IGMP Query messages have been corrected. Also, you may force IGMPv1 messages (which MultiNet 4.4 sent) by setting the kernel variable IGMP_OLD_ROUTER to a non-zero value. [10431] 2-4 Changes and Enhancements Fixed Problems o Corrected an error in which new connections that match an old connection in TIME WAIT state are delayed in starting. [10408] o Corrected an error in memory management on IA64 that can cause data corruption and lead to crashes. [10404] o Errors with filter logging that did not specify a time have been corrected. [10388] o A problem that caused NTY devices to show the wrong connection information in ACCPORNAM in VMS V8 has been corrected. [10375] o The SE0_CONFIGURE.COM example now includes a check for FILTER-SE0.DAT so that it doesn't get skipped when an alternate configuration procedure is provided. [10367] o Fixed a crash that can occur after MULTINET SET/DECNET [10360] o Security improvements in ARP handling code. [10340] o Provided a MultiNet support module for TDC. Note that this must currently be downloaded from the MultiNet V5.1 patces. [10328] o Correct a potential crash due to synchronization errors. [10318, 10324] o Correct a problem in which RAW IP sockets can receive an extra IP header. [10322] o Fixed a problem with a missing #endif in params. [10316] o Corrected an error in defining TCPIP$INET_HOST [10302] o Corrected an error which can cause a system crash when there is an error transmitting an ethernet packet. [10285] o Provided a mechanism to set the maximum queue length for an interface to a different value than it initializes with. [10275] o UCX$IPC_SHR updates for VMS V8.3 [10268] 2-5 Changes and Enhancements Fixed Problems o Subtract the length of the options to be sent as part of TCP packets when sending a packet with MSS data. [10265] o Corrected an error which can cause a system crash while obtaining IP connection information from SNMP. [10252] o The MULTINET SET ARP/FLUSH processing has been modified such that it is now aware of the limits of how many arp entries can be dealt with at one time and it will do the work in a loop if necessary. [10250] o Corrected a crash in the NTYDRIVER. [10222] o Correct an error which can cause a spinwait timeout resulting in a system crash. [10216] o Compute the size required for SIOCGIFCONF when the size provided is zero. This corrects problems with some Java programs. [10205] o Check TCP_MAXPERSISTIDLE for zero, allowing the persist drop function to be disabled. This restores MultiNet V4.4 functionality [10203] o Corrected a bugcheck that can occur when using DECnet Application Services. [10198 ] o Provided support for BSD 4.4 SIOCGIFBRDADDR so that Insight Management Agents V3.3 can work correctly [10197] o Corrected errors in the NTYCP image for Integrity systems. [10194] o Correct an error which can cause socket to not be completely cleaned up upon close that can cause reduced performance on the system. [10187] o Correct an error which can cause a system crash on Alpha or Itanium systems. [10176] o Correct an error which can cause a system crash on VAX systems. [10153] o Improved processing of gethostbyname such that it matches what TCP/IP services returns. [10152] 2-6 Changes and Enhancements Fixed Problems o Added Virtual Private Network support with the GIF interface. [10137] o Corrected error in MultiNet Configure/Menu on VAX. [10127] o Transmit performance improvements on Alpha and Itanium systems. [10120] o Corrected an error in flushing read and write operation queues when a deaccess operation is performed that could result in a system crash due to MULDEALNPAGE, Multiple deallocation of nonpaged pool. [10094] o Increased the number of transmit buffers available to SE interfaces from 16 to 64 on Alpha and Itanium systems. This will improve performance by allowing more transmits to be queued simultaneously. [10085] o Corrected a potential crash for an ICMP message received over an interface that does not have an IP address. [9700] o Multinet now supports the SYS$NET_SERVICES features in OpenVMS 7.0+. The SYS$STARTUP:SYS$NET_ SERVICES_MULTINET.COM file is created during installation, and the required commands are added to MULTINET:START_MULTINET.COM during configuration of the network. SHOW NET, SHOW NET/FULL, START NET, etc. are now supported. [1217] o MultiNet supports SACK (Selective Acknowledgement). This is controlled by the kernel variable TCP_DO_ SACK. [1091] 1 sets TF_WILL_SACK = try to use SACK 2 sets TF_WILL_SACK | TF_IGNR_RXSACK = try to use SACK, but ignore received SACKS SACK is always subject to option negotiation, and defaults to off 2-7 Changes and Enhancements Fixed Problems _____________________________ 2.10.8 Master Server o A change calling $getuai was added to improve performance for Alpha and Integrity systems. [10471] o A potential channel leak in the Master Server (MULTINET_SERVER) process has been corrected. [10437] o Corrected problems with starting auxillary servers. [10343] o Correct a Master Server startup failure when Kerberos v4 is enabled. [10069] _____________________________ 2.10.9 Named o Corrected a problem which could cause an ACCVIO on Integrity. [10156] _____________________________ 2.10.10 NFS o Corrected a potential crash in the NFS_SERVER [10345] o Fixed a problem with acl creation/editing on non-VMS nfs servers [10139] _____________________________ 2.10.11 NTP o Correct errors that prevent local-master or master- clock from working on Integrity systems. [10492] o Correct errors in NTPDATE. [10493] _____________________________ 2.10.12 Printing o MULTINET CONFIGURE/PRINTERS will now allow the slash character in remote LPD queue names. [10236] 2-8 Changes and Enhancements Fixed Problems _____________________________ 2.10.13 RPC o Corrected RPCGEN failure when output was logical name. [10171] o Corrected RPCGEN failure when output was logical name. [10157] o Returning call to decode a double from the XDR stream now correctly calculates the double value. [9894] _____________________________ 2.10.14 R Services o RDATE exits with an error status when it fails to get correct information from the time server. [10429] o Restored an error message in RCP when the source file does not exist. [10363] o Fixed a problem with incoming RLOGIN connections failing due to missing internal symbol(Integrity only). [10326] o Allow mixed case passwords for REXEC with later versions of VMS. [10052] _____________________________ 2.10.15 SFTP/SCP2 o Problems with the SFTP CD command have been corrected. [10381] o SFTP errors in opening text files for write have been corrected. [10365] o Corrected an error with SCP2 not using the specified target file name. [10358] o /NOPROGRESS no longer removes the file transfer completion status line. The progress line is not displayed during the transfer, but a status line is displayed upon completion of the transfer. [DE 10354] 2-9 Changes and Enhancements Fixed Problems o If the logical MULTINET_SFTP_STAT_DESTINATION_FILE is defined to be FALSE, NO or 0 (zero) then the SFTP client will not attempt to do a STAT operation to check for the presence of the destination file before opening the destination file for write. The assumption is that the destination file does not exist. If the logical MULTINET_SFTP_STAT_DESTINATION_ DIRECTORY is defined to be FALSE, NO or 0 (zero) then the SFTP client will not attempt to do a STAT operation on the destination directory before opening the destination file for write. The assumption is that the destination directory exists. These two logicals should be defined to FALSE in order to have the SFTP client work with Sterling Commerce's Connect:Enterprise product. [10276] o Restored /ASCII=VMS to SCP2, omitted for V5.1. [10259] o Fixed an ACCVIO that can occur when exiting SFTP2 from a command file. [10251] o Modified the SFTP server to allow MULTINET_SFTP_VMS_ ALL_VERSIONS to be used no matter what the remote (client) side is. Note that when a file is copied from the VMS system to the client, the filename will contain the version number. [10238] o Correct an ACCVIO when processinmg errors from SFTP protocol version 2 [10234] o If the logical MULTINET_SFTP_DIRECTORY_WITH_ CREATION_DATE is define to True, Yes or 1, then the creation date is displayed in the output for DIRECTORY when operating in VMS mode instead of the modification date. Note that the times are still adjusted by the local offset from UTC. [10179] o FTRUNCATE is no longer done on files that SFTP has opened in text transfer mode. [10172] o Corrected errors in parsing filenames for the SFTP rename and lrename commands [10147] 2-10 Changes and Enhancements Fixed Problems o Corrected errors in the SRI decoding algorithm in SFTP. [10133] o Improved SFTP file size estimation routines to include newline length. [10106] o Added support of FTRUNCATE operation to the SFTP code. [10102] o Corrected an error that would lead to SFTP access violations in batch mode. [10092] o Fixed a problem which would cause some files to be truncated when transferred with SFTP. [10090] o Corrected problems with using SCP/SFTP to transfer files > 5GB. [9866] o Access controls and operation logging have been added to the SFTP server. The logical MULTINET_SFTP_ {username}_CONTROL can be defined /SYSTEM to any combination of NOLIST, NOREAD, NOWRITE, NODELETE, NORENAME, NOMKDIR, NORMDIR, to restrict operations. NOWRITE will disable PUT, DELETE, RENAME, MKDIR, RMDIR; NOREAD will disable GET and LIST. The restriction keywords must be spelt out in full, but puctuation does not matter. The logical MULTINET_ SFTP_{username}_ROOT can be defined /SYSTEM to restrict the user to the directory path specified. (Subdirectories below the specified directory are allowed.) The logical SSH_SFTP_LOG_SEVERITY can be defined /SYSTEM to 20000 to log file transfers or 30000 to log all SFTP operations. The logical SSH2_ SFTP_LOG_FACILITY must also be defined /SYSTEM to specify the lgging class that is used with OPCOM. Values below 5 will use the network class; 5 will use OPER1, 6 will user OPER2, etc. The maximum value that can be specified is 12, which will use OPER8. [9988] 2-11 Changes and Enhancements Fixed Problems _____________________________ 2.10.16 SMTP o Correct a build error that causes an ACCVIO in SMTP on VMS/Itanium V8.2-1 [10235] o Corrected some problems with SMTP and MIME. [10136] o Correct a parsing error in email addresses and return the status to DCL when the email is sent from a DCL command line. [10064] o Two new SMTP logicals were added to allow sending the output of the OpenVMS MIME utility with MultiNet mail: MULTINET_SMTP_ALLOW_MIME_SEND (value is Y/T/1 to enable the new behavior, anything else to disable it) MULTINET_SMTP_MIME_TAG (value is what to look for at the start of the first line of the message. Optional. Defaults to "Mime-version:" Without the SMTP_ALLOW_MIME_SEND defined, the behavior will be as before. WIth it, if the first line of the message file being sent is the mime tag, the blank line at the end of the header output will be suppressed so that the header lines in the message will be seen as header lines rather than message body. [9147] _____________________________ 2.10.17 SNMP o Improved SNMP Agent X code to support Intersystems Cache product. [10353] o Update SNMP to support WBEM$GSVIEW from HP's Insight Management Agents. [10200] _____________________________ 2.10.18 Socket Library o Corrected a problem which can cause MULTINET SHOW commands to ACCVIO. [10473] 2-12 Changes and Enhancements Fixed Problems _____________________________ 2.10.19 SSH o Corrected some problems with SSH handling pre- expired passwords [10330] o The logicals sys$rem_node and sys$rem_node_fullname are now properly defined. [10327] o Increase the length of DNS names that SSH can handle. [10262] o Addresses an accvio which occurred in those cases where the password being verified was not initialized properly. [10182] o When the HP Kerberos V2.1-72 kit is installed on AXP systems, SSH and ktelnet stopped working, and the various Kerberos components (e.g., kadmin) would encounter SYSTEM-F-SHRIDMISMAT errors regarding the TCPIP$IPC_SHR (UCX$IPC_SHR) image. [10099] o SSHKEYGEN/nowarn improperly returned an error message. This has been fixed. [10073] o The CLD causing conflicting SSH utility qualifiers messages has been fixed. [10071] o SSH now creates intrusion records on login failures. [9972] o Failed SSH login attempts now record auditing data. [9842] o A problem where SSH could consume large quantities of CPU time has been fixed. [9020] o SSHKEYGEN can now convert keys from OpenSSH format to the RFC format that we use. [8479] _____________________________ 2.10.20 Telnet o Corrected some security problems with KTELNET. [10217] o Fixed a TN3270 emulation problem when using Telnet client [10183] 2-13 Changes and Enhancements Fixed Problems o Corrected problems with Kerberos 5 Telnet processing on Integrity systems. [10168] _____________________________ 2.10.21 TOPS Library o Corrected ODS-5 filename and directory parsing problems. [10480] _____________________________ 2.10.22 XDM o Errors in the XDM server that can cause it to become unresponsive have been corrected. [10386] 2-14 _______________________________________________________ 3 Documentation Updates This chapter contains a summary of changes to the documentation for MultiNet V5.2. __________________________________________________________ 3.1 MultiNet V5.2 o Changed the MultiNet version number to read V5.2. __________________________________________________________ 3.2 Corrections to the MultiNet V5.2 documentation 3-1 _______________________________________________________ 4 Known Bugs/Issues The following are known bugs and issues with MultiNet V5.2. o There is a problem with RCP and large file transfers. RCP fails to transfer files larger than 2 Gb. [10393] 4-1