Dear SCO Customer, Support Level Supplement (SLS) ptf7069h, the Networking inet Driver for UnixWare 7.0.1, addresses all of the problems listed below. SLS ptf7069a addressed these issues: 1. Traceroute(1Mtcp) fails to trace routing packets to a remote host. 2. Turning the IP_MULTICAST_LOOP option off using setsockopt(3sock) does not disable multicast packets being looped back. 3. A packet received with a different IP precedence value will cause the connection to be reset, without any error indication being sent to the user application. SLS ptf7069b addressed these issues: 4. A panic occurs in rtfree() on a system with more than 32768 routes through one gateway route. 5. Under certain conditions, default routes cannot be deleted ("route delete default" fails). routed(1M) returns the wrong exit code and sends errors to stdout. SLS ptf7069d addressed these issues: 6. Heavy activity on a web server (Netscape or Apache) can cause the server process to hang due to incorrect handling of incoming TCP connections. 7. A streams leak in the tcp driver which could result in process hangs. SLS ptf7069e addressed this issue: 8. Enhancement to provide gratuitous arp functionality (-i option) arp(1Mtcp) -i interface_name target_ipaddr Send an ARP request, avoiding the cache, on the specified interface interface_name (for example, net0). In the broadcast request, the sender's IP address is that of the interface, the sender's hardware address (MAC address) is that of the interface, and the target IP address is that specified by target_ipaddr. On interfaces with aliased IP addresses (see ifconfig(1Mtcp)), a separate ARP request is broadcast for each alias address with the sender's IP address set to the alias address. As generally used, the sender expects the host with the target IP address to respond with an ARP reply containing its hardware address. If the sender and target IP addresses are identical, a gratuitous ARP request is broadcast. This allows other hosts on the network to update their cache entries for the sender's IP address with the hardware address contained in the request. No reply is expected. If an interface has been configured with several alias IP addresses, a separate gratuitous ARP request must be issued for each IP address which needs to notify its corresponding hardware address to the network. SLS ptf7069f addressed these issues: 9. A PANIC in function in_memcmp() called by rt_output() in router. 10. The following warning messages were logged on importing the internet bgp routing table via gated: WARNING: rn_delete couldn't find out annotation WARNING: rn_delete Orphaned Mask 11. System panic when pinging multicast address 224.0.0.X due to ip_output() failing to check for null value of imo. SLS ptf7069g addressed these issues: 12. Applications that use t_optmgmt() can cause PANIC. 13. Opens/closes of /dev/arp in a loop will eventually fail with ENXIO. Subsequently, all opens of /dev/arp will fail with ENXIO (for example 'arp -S'). SLS ptf7069h additionally addresses this issue: 14. System hangs and the osmlog displays the message: NOTICE: Kernel virtual memory for buffer I/O temporarily exhausted; using reserved pool to allow paging to proceed. Contents -------- /etc/conf/pack.d/inet/Driver_atup.o /etc/conf/pack.d/inet/Driver_mp.o /usr/sbin/arp Software Notes and Recommendations ---------------------------------- SLS ptf7069h should only be installed on: UnixWare 7 Release 7.0.1 Installation Instructions ------------------------- 1. Download the ptf7069h.Z file to the /tmp directory on your machine. 2. As root, uncompress the file and add the SLS to your system using these commands: $ su Password: # uncompress /tmp/ptf7069h.Z # pkgadd -d /tmp/ptf7069h # rm /tmp/ptf7069h 3. Shut down and reboot the system after installing this SLS package. The release notes displayed prior to installation can be found in: /var/sadm/pkg/ptf7069/install/ptf7069.txt Removal Instructions -------------------- 1. As root, remove the SLS package using these commands: $ su Password: # pkgrm ptf7069 2. Reboot the system after removing this SLS package. If you have questions regarding this SLS, or the product on which it is installed, please contact your software supplier.