VSI TCP/IP Services for OpenVMS V6.0-30

An issue has been identified in the current NTP implementation where configuring the minpoll parameter to a value of 8 or higher may cause the local clock to gradually lose synchronization with the NTP server. In some cases, this results in an increased time drift or a broadening of the synchronization interval relative to the server’s reference clock. This behavior is under investigation, and users are advised to use lower minpoll values to maintain accurate synchronization.

After upgrading from TCP/IP V5.7 to TCP/IP V6.0 without first disabling SSH (as detailed in Section 7, ''Upgrading From TCPI/IP Services V5.7''), users may encounter the following error messages upon starting the stack:

%TCPIP-S-STARTDONE, TCPIP$TELNET startup completed
%TCPIP-E-STARTFAIL, failed to start SSH
-TCPIP-E-NOSERVREC, cannot find SSH service database record
%TCPIP-E-STARTFAIL, failed to start SSH_CLIENT
-TCPIP-E-NOSERVREC, cannot find SSH_CLIENT service database record
%TCPIP-S-STARTDONE, TCP/IP Services startup completed at 5-MAY-2025 21:24:34.75

These error messages can be safely ignored. Alternatively, you can get rid of them by entering the following commands:

$ TCPIP SET CONFIG ENABLE NOSERVICE SSH
$ TCPIP SET CONFIG ENABLE NOSERVICE SSH_CLIENT

The TCPTRACE utility is not currently supported for x86-64 releases of VSI TCP/IP. VSI suggests using the TCPDUMP utility, as it provides comparable functionality and is supported on all architectures (Alpha, IA-64, and x86-64).

If the FTP service does not work after it has been started, switch to passive mode with the following command:

FTP> SET PASSIVE ON
Passive is ON

In passive mode, the FTP client always initiates a data connection. This is useful in virtual machine environments when there is network address translation (NAT) in your network.

To run this command automatically when you invoke FTP, put it into SYS$LOGIN:FTPINIT.INI. For the full description of the SET PASSIVE command, refer to the relevant section in the VSI TCP⁠/⁠IP Services for OpenVMS V6.0 User's Guide.

In VSI TCP/IP Services V6.0, the DHCP client and failSAFE IP cannot be activated for the same NIC, because both DHCP client and failSAFE IP manage the address assignment of a NIC. You must select one or the other.

NTPDATE is no longer supported and will be removed from an upcoming release of VSI TCP/IP Services V6.0. To perform the equivalent of NTPDATE, run NTPD as follows:

$ ntpd :== $TCPIP$NTP 
$ ntpd "-G" -q

The forwarders' addresses and the DNSSEC validation are set up in the following lines in the SYS$SPECIFIC:[TCPIP$BIND]TCPIP$BIND_CONF.TEMPLATE_FORWARD template file:

//Specifies the IP addresses to be used for forwarding.
//The default is the empty list (no forwarding).
forwarders {
    8.8.8.8;
    8.8.4.4;
};
 
dnssec-validation auto; //Enable DNSSEC validation.
                        //Note dnssec-enable also needs to be set to
                        //yes to be effective. The default is yes.

However, if forwarders are changed to DNS servers that do not support DNSSEC or have it disabled, DNS lookup replies will be discarded when the DNSSEC validation fails.

dnssec-validation auto

Previously, the NFS client connected to an NFS server running on a UNIX-like platform could crash when handling an RPC response payload larger than 64 KB. This issue has been resolved.

Previously, a file caching issue could cause the NFS client to reflect an updated directory listing after a PURGE command with a significant delay. In this release, the file caching behavior has been corrected to ensure that directory listings are updated without delay.

Previously, the NFS client would occasionally crash while processing NFS COMMIT operations, due to unexpected input parameters being passed to the COMMIT function. In this release, the function properly validates all parameters.

The command TCPIP SHOW VERSIONS and the TCPIP$VERSIONS utility have been modified to include the maintenance release information in addition to the major and minor version numbers of the installed TCPIP kit.

Previously, the VSI TCP/IP SYSCONFIG parameter SCTP:SCTP_THREAD was placed in the wrong section of the configuration file. This issue has been resolved in this release, and a new template configuration file has been included in the kit. VSI recommends that all customers update their configuration using this new template configuration file. The file can be extracted via the following command:

$ LIBRARY /EXTRACT=SYSCONFIGTAB/OUT=TCPIP$ETC:SYSCONFIGTAB.TEMPLATE -
SYS$LIBRARY:TCPIP$TEMPLATES.TLB

Previously, if the protection attributes of a file were updated on the NFS server or client, the client would fail to display the changes. This issue has been resolved, and the attributes are now displayed correctly.