These release notes support V4.6.1 of the ptx®/TCP/IP software intended for use with NUMA-Q® and Symmetry® systems. Read this document before you install and run this release of the ptx/TCP/IP software.
The following software products are prerequisites for the ptx/TCP/IP V4.6.1 software product:
To enable porting of various third party applications to DYNIX/ptx, ptx/TCP 4.6.0 libraries (with some exceptions) have been modified to conform to the POSIXTM threads standard.
ATTENTION The ABI sockets library (libsocket.so.1) is NOT thread-safe.
Binaries compiled on ptx/TCP V4.1.x or later should not specify -linet to link with libinet.so. libinet.so does not contain any useful function in these releases. libinet.so is provided so that binaries built on ptx/TCP V4.0.x and earlier may run on later versions.
The following libraries/modules are thread-safe:
Note that the following libraries are not part of ptx/TCP, but are thread-safe:
The following libraries/modules are not thread-safe:
The following APIs are thread-safe and have no changes to their interfaces:
herror()
getmyinaddr()
getpeerinaddr()
inet_addr()
inet_network()
inet_makeaddr()
inet_lnaof()
inet_netof()
link_addr()
The following functions have been made thread safe without any change in their use except that they might fail with h_errno set to ENOMEM. This can happen when the system is low on memory and the implementation is not able to allocate thread-specific data.
gethostbyname()
gethostbyaddr()
getnetbyaddr()
getnetbyname()
getprotobyname()
getprotobynumber()
getservbyport()
getservbyname()
The following APIs cannot be made thread-safe without changing the interfaces. Therefore, the existing functions are left unchanged, but a new set of functions is provided.
Function |
Thread-safe Alternative |
inet_ntoa() |
inet_ntoa_r() -- additional argument: 16 byte character buffer |
link_ntoa() |
link_ntoa_r() -- additional argument: 64 byte character buffer |
Interfaces with no change:
The following APIs are left unsafe. These calls should be made on a per-process basis. Typically, multiple threads in the same process do not make these calls simultaneously. If they need to do so, an appropriate synchronization mechanism needs to be followed.
syslog()
openlog()
closelog()
setlogmask()
gethostent()
sethostent()
endhostent()
getnetent()
setnetent()
endnetent()
getprotoent()
setprotoent()
endprotoent()
getservent()
setservent()
endservent()
res_query()
res_search()
res_mkquery()
res_send()
res_init()
dn_comp()
dn_expand()
rcmd()
rresvport()
t_rcmd()
t_rrcmd()
t_rresvport()
t_cresvport()
ruserok()
rexec()
struct _res_state _res
The resolver routines use this global structure to maintain the global configuration and state information of the resolver.
This data object is left UNSAFE and cannot be used in multiple threads simultaneously. However, the calls to resolver by getXXXbyYYY() routines are thread-safe, because they have been serialized, using a mutex lock.
The NUMA quad-based architecture imposes a high cost on cross-quad traffic. To achieve higher speeds, listener processes in a system can be run on the same quad as the interface on which the data is expected for the listener. This is achieved by assigning different addresses (on the same subnet) to interfaces, and binding the listening endpoints to those addresses. Because of this setup, the data received by the server follows the most efficient path to the listening application.
To achieve quad-specific output, multiple interfaces can be linked in a multidrop set and output to any of the interfaces will be delivered through a quad-local member of the set, if there is one. This avoids costly cross-quad transfer of output data and can result in better throughput.
Improvement might also be the result of greater than media speed throughput on the same IP subnet if it is a switched network. For example, traditional ethernet setups can support only 100 Mbps on the wire. In a switched setup, multiple hosts can communicate at 100 Mbps while on the same IP subnet. With multidrop this becomes an additional advantage since the output will go out different interfaces rather than being directed out the one interface to which the route points.
This is not a general solution. To achieve the best results, you must customize the system for optimum performance.
ATTENTION The multidrop parent interface is for reference only. ifconfig commands will not work with it.
Use the ifadmin utility to create multidrop interfaces and child interfaces linked to a parent. Support of multidrop includes the following ifadmin options:
/etc/ifadmin multidrop <name>
/etc/ifadmin link <parent name> <child name>
/etc/ifadmin unlink <parent name> <child name>
Here is an example:
# /etc/ifadmin multidrop md0
# /etc/ifadmin link md0 pe0
# /etc/ifadmin link md0 pe4
# /etc/ifadmin link md0 pe8
Use the multidrop option to ifadmin to create a multidrop interface. After creating an interface, administrators can add one or more (non-multidrop) interfaces as children of the multidrop interface. Output to any of the child interfaces is sent to the nearest (in terms of quad location) child interface for output. The ifadmin unlink option removes an interface from consideration for output that is done through the multidrop interface.
ATTENTION The interfaces forming a multidrop must conform as follows:
All must have the same type (for example, all ITX or all Ethernet).
All must have compatible flags (identical except for RUNNING and UP).
All must have identical MTUs.
The FreeBSD resh Version 8.3 has been ported to ptx/TCP V4.6.0. This replaces the earlier TLI-based implementation distributed with ptx/TCP.
New command arguments are as follows:
The ftp distributed from ptx/TCP V4.6.0 onwards will be a BSD sockets-based implementation as compared to the TLI-based version distributed in the previous ptx/TCP releases. This is a port of FreeBSD ftp Version 8.4.
Note the following changes in the commands supported by ftp.
New Command Line Option
Also if the ftp binary is renamed as pftp or if the environment variable FTP_PASSIVE_MODE is defined, ftp operates in the passive mode.
New ftp Commands
chmod mode filename
Changes the permissions models of the specified filename on the remote system to mode.
idle [ seconds ]
Sets the inactivity timer on the remote server to the specified seconds. If seconds is omitted, the current inactivity timer is printed.
modtime filename
Shows the last modified time of the specified filename on the remote system.
newer filename
Gets the file only if the modified time of the remote file is more recent than the file on the current system. If the file does not exist on the current system, the remote file is considered newer. Otherwise, this command is identical to get.
nlist [ remote-directory ] [ local-file ]
Prints a list of the files in a directory on the remote machine. If remote-directory is left unspecified, the current working directory is used. If interactive prompting is on, ftp will prompt you to verify that the local-file argument is indeed the target local file for receiving nlist output. If no local-file is specified or if the local-file contains only a dash (-), the output is sent to the terminal.
reget remote-file [ local-file ]
reget acts like get, except that if local-file exists and is smaller than remote-file, local-file is presumed to be a partially transferred copy of remote-file and the transfer is continued from the apparent point of failure. Use this command when transferring very large files over networks that are prone to dropping connections.
remotestatus [file-name ]
With no arguments, shows status of remote machine. If file-name is specified, shows status of file-name on remote machine.
restart marker
Restarts the immediately following get or put command at the indicated marker. On UNIX systems, marker is usually a byte offset into the file. restart can be used to specify the byte offset from where the subsequent get/put should fetch the file, while reget starts from the apparent point of failure (depending on file size of previously transferred file).
site arg1 arg2
The arguments specified are sent verbatim to the remote FTP server as a SITE command.
size file-name
Returns the size of file-name on the remote machine.
system
Shows the type of operating system running on the remote machine.
umask [ newmask ]
Sets the default umask on the remote server to newmask. If newmask is omitted, the current umask is printed.
Changes in the .netrc File
The .netrc file contains login and initialization information used by the autologin process. It resides in your home directory. The .netrc file will recognize the token default.
This is the same as the machine name except that the default matches any name. There can be only one default token and it must be after all machine tokens. This is normally used as follows:
default login anonymous password user@site
This gives you an automatic anonymous ftp login to machines not specified in .netrc. This can be overriden by using the -n flag to disable autologin.
Commands Dropped in This Release
The FreeBSD ftpd Version 8.4 has been ported to ptx/TCP/IP V4.6.0. This replaces the earlier TLI-based implementation distributed with ptx/TCP/IP.
-D Option
The -D option allows ftpd to detach and become a daemon, accepting connections on the FTP port and forking children processes to handle them. This involves less overhead than starting ftpd from inetd and is, therefore, useful on busy servers to reduce load.
-R Option
The -R option allows ftpd to revert to historical behavior with regard to security checks on user operations and restrictions on PORT requests. Currently, ftpd will only honor PORT commands directly to unprivileged ports on the remote user's host (which violates the FTP protocol specification but closed some security holes).
-S Option
The -S option allows ftpd to log all anonymous transfers to the file /var/log/ftpd when this file exists. The anonymous transfer logs will not be written to EES since these are neither events nor error conditions of ftpd. This is a security measure of logging all anonymous ftp transfers.
-T maxtimeout Option
This option specifies the maximum timeout period that a client can request. The maximum period allowed can be set to maxtimeout seconds with the -T option. The default is two hours.
-a address Option
This option has an effect only when the -D option is specified. After specifying both options, ftpd will accept connections only on the specified address.
-p file Option
This option has an effect only when the -D option is specified. After specifying both options, ftpd will write the daemon's process ID to a file.
-A Option
This option allows anonymous ftp access.
The following non-standard or UNIX specific commands are supported by the SITE request:
MDTM and SIZE are not specified in RFC 959, but will appear in the next updated FTP RFC.
You can use the /etc/nologin file to disable ftp access. If this file exists, ftp displays it and exits. If the /etc/ftpwelcome file exists, ftp prints it before issuing the ready message. If the /etc/ftpmotd file exists, ftp prints it after a successful login.
If a STAT command is received during a data transfer, preceded by a Telnet IP and sync, transfer status will be returned.
ftpd does an additional authentication of users as follows:
The login name must not be a member of a group specified in the /etc/ftpusers file. Entries in the file interpreted as group are prefixed by an @ sign. The user must have a shell listed in the /etc/shells file. If a user name appears in the /etc/ftpchroot file, or the user is a member of a group with a group entry in this file (that is, one prefixed with @) the session's root will be changed to the user's login directory by chroot for an anonymous or ftp account. However, the user must still supply a password. This feature is a compromise between a fully anonymous account and a fully privileged account. The user's account should be set up with the same considerations as an anonymous ftp account (for example, with local bin, etc, and lib directories).
If the system has multiple IP addresses, ftpd supports the idea of virtual hosts, which allows you to define multiple anonymous ftp areas, each one allocated to a different internet address. The /etc/ftphosts file contains information pertaining to each of the virtual hosts. Each host is defined on its own line, which contains a number of fields separated by white space:
Defining a virtual host for the primary IP address or host name changes the default for ftp logins to that address. You can leave the user, statfile, welcome, and motd fields blank, or use a single hyphen (-) to indicate that the default value should be used.
The following new files affect the behavior of ftpd:
This ftpd does not have the command line option -m, which the previous version used to log anonymous ftp sessions.
Since this ftpd is a sockets-based implementation, the entry in inetd.conf should be as follows:
ftp stream tcp nowait root /usr/etc/ftpd ftpd
This will be ensured at installation time.
The ifconfig command distributed with previous versions of ptx/TCP/IP was not consistent in reporting errors. This made the writing of scripts difficult. The ifconfig in ptx/TCP/IP V4.6.0 reports the following error codes:
ATTENTION ifconfig will attempt to set the interface flags only if the new flags being specified are different from the flags already set on the interface.
ptx/TCP/IP V4.4 and V4.5 implementations required you to add the LLC header size to the MTU being assigned to an interface. This has been modified to be consistent with industry standards. The interface MTU now corresponds to the data portion only and does not include the LLC header.
For example, the ethernet MTU is now 1500 (not 1502). If you use SNAP, it is 1492.
telnet has been modified to negotiate options only if the remote host is a telnet port. If the remote port is prefixed with a dash or minus sign (-), then it is taken to be a telnet port. The default telnet port is 23.
The default mode on startup is character-at-a-time. The default modes may be overridden by specifying the desired mode in .telnetrc or by specifying the mode after escaping to the telnet prompt.
The maximum UDP datagram that may be sent is limited by STRMSGSZ or (65535 - size of UDP and IP headers), whichever is smaller. The size of UDP and IP header without options is 28 bytes. Thus, the maximum UDP datagram is 65507 bytes. The presence of IP options increases the IP header size. This will further reduce the corresponding maximum datagram size. Previously, ptx/TCP/IP had a limit of 16K on UDP message size. The STRMSGSZ limit can be configured by setting the kernel parameter STRMSGSZ. The lower bound specified for STRMSGSZ is 16K.
ATTENTION BSD sockets are not affected by STRMSGSZ value. The maximum datagram size when using the BSD sockets API has always been 65535 - (size of (UDP + IP headers)).
In versions of ptx/TCP/IP V4.5.x, the packets sent to the local interface (which are looped back) were not seen by tcpdump. To enable tcpdump to see these packets, do the following:
tcpdump -i gloop
The global loop (gloop) interface is not really an interface. tcpdump will issue the following warning:
tcpdump: WARNING: SIOCGIFADDR: gloop: Invalid argument
Ignore this warning. tcpdump will now show all packets sent to any of the local interfaces. Further filtering based on the exact IP address is possible.
rarpd over LANE is not supported.
IP reassembly buffers are no longer allocated statically. The MAX_REASSQ configuration parameter has been dropped. Instead, two new parameters are used:
In previous versions of ptx/TCP/IP, the inpcb and tcpcb structures were statically allocated at boot time according to a pre-configured limit. This had several drawbacks:
The limit could not be altered without rebuilding the kernel and rebooting.
An excessively high limit wastes memory.
Allocations could not be made local to each quad.
Lower performance is caused by false sharing of cache lines.
Protocol control blocks (PCBs) used by ptx/TCP/IP V4.6 are now allocated dynamically as needed, rather than statically at kernel build time (as was the case in the past). This affects the method used to configure the number of PCBs as follows:
The parameters N_TCP_PCB_FREE, N_UDP_PCB_FREE, and N_RAW_PCB_FREE no longer exist. The parameter MAX_IP_PROTO undergoes a name change (it becomes N_DEV_IP, described below).
The following new parameters appear:
NSOCKET - This is the number of sockets you may allocate system-wide. Note that almost everything in TCP is now a socket; in particular, BSD sockets, ABI sockets and TLI opens of /dev/tcp or /dev/udp are all actually sockets. Opens of /dev/ip and COFF binaries using UNIX domain sockets are not really sockets underneath. For initial kernel configuration, the value of NSOCKET may be set to the sum of the old N_TCP_PCB_FREE, N_UDP_PCB_FREE, and N_RAW_PCB_FREE parameters. Note that, since memory is not allocated until sockets are used, there is no up-front memory penalty for padding NSOCKET with extremely high values.
The socket limit (which is initalized by NSOCKET) may be changed while the system is running via kmstune of the tcp.socket pool.
N_DEV_TCP, N_DEV_UDP, N_DEV_IP - These are the number of STREAMS opens of /dev/tcp, /dev/udp and /dev/ip allowed. These limit the number of ABI sockets and TLI endpoints, each of which consumes one stream for either /dev/tcp or /dev/udp. These parameters are not dynamically configurable (these are the number of devsw_allocs done at boot time for the respective devices). Within TCP, rlogin and telnet are both TLI-based, and consume /dev/tcp streams.
Note that these parameters are not tunable at runtime.
N_DEV_IP is MAX_IP_PROTO, with the name changed to make the nomenclature consistent.
The kmstune adjustable structure pools used are named tcp.socket, tcp.socket_peer and tcp.vnode. The socket_peer and vnode pools are implicitly limited by the socket pool; so there is no need to explicitly limit them.
ATTENTION If you install ptx/TCP/IP V4.6.1 on a system that has earlier versions of ptx/TCP/IP, you will find that the following TCP/IP kernel parameters will be deleted from the site files:
To install ptx/TCP/IP V4.6.1, refer to the DYNIX/ptx V4.5.0 and Layered Products Software Installation Release Notes.
ATTENTION If you are installing ptx/TCP/IP V4.6.1 over a previous version of ptx/TCP/IP, you need to perform the following steps to ensure a successful installation. If you are performing a scratch install, you can ignore the rest of this caution.
During the installation, you may need to modify the preview log for ptx/TCP/IP.
Carefully examine the CONFLICTS entries in the preview.log file that are generated by the ptx/INSTALL program. The default answers might not be what you want.
Files such as /etc/hosts, /etc/services/, and etc/hosts.equiv might have a value of REPLACE rather than SKIP. You will need to restore your original files after the installation or change REPLACE to SKIP for the CONFLICTS entries in the preview.log file during the installation to ensure that your host-specific custom files are preserved.
ptx/TCP/IP replaces the /etc/services file. If ptx/CLUSTERS is also installed on your system, this action will remove the ptx/CLUSTERS information from the file. To retain the information, you must change the preview log entry for /etc/services from CONFLICT-REPLACE to CONFLICT-SKIP.
ATTENTION The reshd, ftpd, and rexecd distributed with this release are BSD-sockets based and not TLI implementations. reshd was a TLI implementation until ptx/TCP/IP V4.4.1. In ptx/TCP/IP V4.6.0, rexecd will be disabled by default. Upon installing ptx/TCP/IP V4.6.0, inetd.conf entries, such as
ftp tli tcp nowait root /usr/etc/ftpd ftpd
shell tli tcp nowait root /usr/etc/reshd reshd
exec tli tcp nowait root /usr/etc/rexecd rexecdwill be modified to the following:
ftp stream tcp nowait root /usr/etc/ftpd ftpd
shell stream tcp nowait root /usr/etc/reshd reshd
#exec stream tcp nowait root /usr/etc/rexecd rexecdAlso note that this change in inetd.conf will occur irrespective of choosing CONFLICT-SKIP or CONFLICT-replace. The inetd.conf being replaced will be saved in /usr/options/tcp/inetd_conf/inetd.conf.
The documentation for the ptx/TCP/IP V4.6.1 release consists of the following manuals:
ptx/TCP/IP Overview
ptx/TCP/IP Administration Guide
ptx/TCP/IP Programming Manual
ptx/TCP/IP Sockets Manual
ptx/TCP/IP Kernel Error Messages
ATTENTION Time synchronization on Symmetry systems can be affected by the bootflags command.
You can start the time daemon /usr/etc/xntpd at boot-time by uncommenting the appropriate lines in /etc/rc2.d/S50netservers. This is advisable only if you invoke /usr/etc/ntpdate -b before the xntpd starts, otherwise the time delta between the host clock and the reference clock might be too large for the xntpd daemon.
On Symmetry systems the system time will be adversely affected by the execution of a bootflags command with options that display the firmware boot parameters: -bh, -bs, -bo, and -bv. Using bootflags with these options has the side-effect of suspending the system clock for several tens of milliseconds. This error will quickly be corrected by the normal operation of xntpd. You should not execute multiple bootflags -bx commands in succession. Doing so will slow the clock faster than xntpd can handle as it attempts to correct the time. The bootflags -bx commands should be used infrequently to avoid introducing a large cumulative error in the system time.
On clustered systems the bootflags problem can cause this warning message to be printed during boot:
WARNING: Time in the cluster is NOT synchronized to within 100 msecs!
During boot the /etc/rc2.d/S99scandump script executes a bootflags -bh command. Shortly after that the /etc/rc2.d/S99cta_in script executes /usr/bin/clust_check_time, which compares the system time to the time on the other clustered nodes. Because xntpd has not had much time to adjust the clock after the bootflags command, the delta may exceed 100ms. If you see this message you can check the system time again a few minutes after boot to verify that xntpd has synchronized the time with the other clustered nodes.
This problem does not occur on NUMA-Q systems.
Multiple SYNs may not be unique if connection requests arrive while the system clock has not changed (the system clock has a 10-millisecond resolution).
Sendmail expects the local host name to be a fully qualified domain name. To check that it has a fully qualified host name, it expects to see at least one dot in the name. If it does not find a dot in the name, it will assume that there was an error in the name lookups, and will pause for a period of time waiting for the name server to settle out. This causes an unnecessary delay for /etc/host based systems that do not fully qualify their host names.
Workaround: Add an alias to the host that contains a dot at the end of the name, as in the following example:
10.1.2.3 myhost myhost.
Lack of support for the old IP_GET_IF_CONFIG ioctl breaks COFF compatibility for the RPC library. Old COFF binaries which use IP_GET_IF_CONFIG ioctl will no longer work.
routed can flip flop the routes between aliases if they exist on the same subnet.
Workaround: Avoid aliases on the same subnet, if possible.
The ifconfig -a command lists the pathname of the device. If the device clone information is not found in the /etc/devinfo file or there is no devinfo file for the device, then /dev is searched for the actual device entry. This slows the command down.
The following problems were fixed in this release of ptx/TCP/IP:
247799 - Multidrop Failover Does Not Work
An interface of a multidrop set can fail over to another interface within the set. Incoming datagrams sent to the failed interface will then be delivered to the host through the other interface.
Outgoing datagrams will always pick an interface that is "up" from the mutidrop set, avoiding interfaces that are "down."
249368 - chroot Commands During Install Dump Core
ptx/LIP, which is part of the base OS, takes care of this problem.
249793 - DHCPD Sends Out Bogus Responses After Applying Fix for PR#229759
250207 - TCP Install Needs to Be Smarter about Old Site Configuration Files
When ptx/TCP/IP is installed, it will remove the following parameters from your local site file. These parameters are either obsolete or have been replaced by other parameters.
N_TCP_PCB_FREE
N_UDP_PCB_FREE
N_RAW_PCB_FREE
MAX_REASSQ (replaced by MAX_IPQ_HDRS and MAX_IPQ_NODES)The ptx/TCP/IP installation performs the following actions:
250245 - udp_sendspace Should Be User Configurable (Like tcp_sendspace)
udp_sendspace and udp_recvspace are now configurable through UDP_SENDSPACE, UDP_RECVSPACE. Default values are 9 and 41. These values are in units of 1K bytes.
250294 - tcpdump Has Problem Working with ATM Interfaces
tcpdump now supports -C option to print circuit header information for circuit oriented media (atmraw, atmclip and atmlane). Refer to the tcpdump(1) man page for details.
250782 - System Reporting TCP ARP .. Moved Messages
Whenever the MAC address corresponding to an IP address changes, a message of the following form appears in ktlog:
arp: <IP address> moved from <old MAC address> to <new MAC address>To disable this message, use the menu to set ARP_NOTIFY_MAC_CHANGE to 0 and rebuild the kernel.
251462 - FUNC 3N Sockets Man Pages Shown by Default, No Mention of BSD Version
The default man pages for socket calls list the ABI version and not the BSD version. The BSD version is listed under section 2 of the man pages of the corresponding socket call.
The following problems were fixed in ptx/TCP/IP V4.6.0:
23771 - "+" Operator Has No Effect in .rhosts file
213561 - ftpd Should Handle -t 10 as Well as -t10
215966 - ftp Macros in .netrc Limited to 4096 Bytes
217860 - /etc/rmt Behavior Is Wrong and Does Not Match Man Page
218411 - Would Like to Change reshd Path
218859 - timedc Exits on Second ^c
218871 - resh Does Not Flush Its Buffers on Some Errors
219666 - /usr/etc/netsettime Has No Man Page
220072 - telnet Should Support Window Size Negotiation Option
222422 - ftp Displays "No Error" When a Large File Is Incompletely Sent
223452 - flioctl Should Deregister/Register When NOSNAP Flag Changes
225198 - keepalive Probes Should Be Switchable on TCP Daemon Command Line
228978 - REINITIALISE Functionality for ftpd Required
229759 - dhcpd Dumps Core
230438 - ifconfig Lets You Bind Interfaces with Overlapping Routes
232612 - ifconfig Uses dest_addr to Update Broadcast Address
233038 - We Can Execute More Efficiently by Coalescing Headers in One Buffer
233151 - ifconfig Exit Status Is 0 on Setting Broadcast Address as User
234193 - Need More Robust ifconfigall Command
234533 - netstat -C Reports Incorrect Device Attachments
234902 - bind() with namelen < Address Size Should Return EINVAL
235354 - Mystic Meg Could Out Guess netstat -D - Wrong Device Names
236046 - Enhanced User/Anonymous Access Required for ftpd
236245 - sockmod Out of Bounds Processing Still Has Prodigious Appetite for mblks
236707 - IP Reassembly Could Be Better
237052 - FUNC MSGS validate_ifs Give Incomplete Error, Cannot Add New Device
237428 - newaliases Man Page Is Confusing- Two Locations for Aliases File
237508 - ifconfigall Fails with "undefined" with Different Length pe Devices
237639 - Make Inverse ARP Shows ATM Circuit Number When It Fails
238097 - Need Dynamic Allocation of pcbs
238456 - Add Support for Channel Attach to ptx/TCP/IP
238488 - Sendmail Does Not Recognize Multiple Interfaces as Local
238546 - .rhosts Ignores the "+" Symbol
238990 - Extra ACK from Listener When Using Large Windows
238994 - ftpd Once Again Is Stupid About ABOR
239052 - Local Interface Address Packets Looped Back Not Seen by tcpdump
239106 - ifconfig Not Consistent in Reporting MTU
239522 - Sendmail Will Not Use resolver Libraries, If NFS Is Not Installed
239523 - ifconfig Returns Wrong Status
239525 - tcpdump Comes Out with a -1 When Given Wrong Options
239608 - ifconfig Reports Error on Adding Aliases, Does the Job
239702 - ip_reass Has a Buffer Leak
240120 - syslog with setlogmask() Logs Unexpected Messages
240186 - makeroute Does Not Clean Up llinfo's for Cannot Insert Routes
240355 - syslog() Blocks on a write
240361 - Add netstat Support for tcps_pawsdrop
240418 - Need Multipe Interfaces on Same Subnet
240770 - We Should Make Multi-Homed, Same-Subnet Routing More Quad Aware
240800 - Need Entry for CPAdmin in /etc/services
240802 - UDP Should Allow Packets of Size > 32k (Needed for NFS Version 3)
240914 - ping -r Does Not Return Network Unreachable for Remote Networks
241212 - Buffer Leak with netperf UDP Bulk Data Tests
241357 - SYS: PANIC: TCP: rtentry_remove: Route Table Unlocked
241459 - Typo in looutput() Causes All Packets to Be Sent to BPF
241505 - No Raw Mode Network Communications Software Available in ptx
241539 - so_setown() Can Clear so_pgid and so_pgref Without Holding Lock
241605 - ping -r to Local Address Does Not Work
241888 - Can MMU Fault on Allocation Failure in fl_bring_up()
241986 - Allow Remote Login Only If the User's Login Region Is Active
241995 - Illegal Host Names Used in named.hosts Example File
242243 - tcpdump Is Unable to Read Sniffer Format File Properly on FDDI
242354 - allocb Failure Under Hostility Cases System to Hang at Boot
242362 - route -a Does Not Get Executed from S50TCP If initdefault Is 3
242520 - Inverse ARP Entries Are Not Tagged for Display
242522 - TCP Does Not Support Options Passed Down by t_connect()
242870 - The MTU Should Not Include the Type and LLC/SNAP Portion of the Frame
242976 - Compatibility of MQSeries on 4.4.4 and Earlier OSs - socketvar.h
243023 - SO_DONTROUTE/MSG_DONTROUTE Do Not Work on UDP Sockets
243044 - MENU: Change IF Address and Flags Reports Error Even When Successful
243141 - SIOCSIFBRDADDR Sets Junk Value
243234 - UDP Data Received Over a Connected sockmod Socket Is Dropped
243257 - ftp mdir Command Broken for Local Files Other Than stdout
243258 - Packet Drop Count Not Done When Interface Flushed
243261 - SNMP route dump Panics Manufacturing Kernel - Does Not Work In Standard Kernel
243277 - ftp Command Only Expands Wildcard on one End
243320 - print_slippage() Can Corrupt Memory on Systems Greater Than 32CPU
243458 - Hostility Panic in sbag_rprocess
243488 - Ethernet Type MAC Broadcast Address Sent on an ATM Circuit
243515 - netstat -m Displays Bad UDP Values
243630 - Possible Memory Leak in fl_circ_notify() in Low Memory Conditions
243696 - getsockname() Panics if unp_addr is NULL
243706 - netstat -i Needs Unsigned printf Conversion for Packet Traffic
243708 - PANIC: Infinite MMU Page Fault Sequence: Faulting KVA = 0x4
243873 - named Does Not Bind a Listener to Alias IP Address of an iInterface
243903 - getpeername Handling of Unbound Socket Panics System
243931 - butler4, Take 2. Hang, Forced Panic from WT_LOCK Contendees
243958 - Panic str: tcpmux_ursrv: No sbag
243966 - TCP stuck in CLOSE_WAIT Forever Under Certain Circumstances
243995 - Problem with tcpdump While Listening to Packets on Loopback
244118 - mib2agt Does Not Return Statistics for FDDI Interfaces
244134 - connect Leaks Message Blocks Allocated by sockargs
244192 - TCP Does Not Allow Zero Length Source Hardware Address Type in InvArp Request
244288 - ip_options Not Handled in udp_output
244316 - tcpmux_ursrv Can Exit Without Releasing Socket Lock
244344 - Man Page for getnetbyaddr Gives Wrong Type
244346 - We Need Some Way to Create Permanent Direct Host Routes
244466 - Need Option to Ignore ARP Hardware Type
244541 - TCP Keeps ARPing About MAC Address Change for Tokenring
244550 - Func: MMU Fault from FastLAN Test
244565 - Wrong Error Number Returned by connect()
244584 - Routing Sockets Doing Badness/No grok mpcntrs
244606 - ticotsord Still in the sockaddr_un Dark Ages
244692 - syslogd Man Page References Wrong Header File Location
244697 - SYS:Panic Assertion Failed: sopp->sop_refcnt > 0 on elm17b40
244701 - Authentication Does Not Work in routed
244744 - inetd Spins After Aborted Connection Request
244768 - ping seems to Fail Subsequent Pings After 1 Loss
244780 - ICMP_GET_MIB_STATS Returns Incorrect Values
244781 - copy_rt_mib Does Not Copy Appropriate Information for rt_nexthop
244782 - subagent uses OBSOLETE_TCP_GET_PCBS ioctl to Get TCP PCB Information
244897 - TCP Can Lose ARP Entry for ATM PVC
244899 - Buffer Leak in flsendloop
244900 - Race Between floutput/fl_notify() Can Panic System
244916 - ifconfigall Does Not Handle the "no interfaces" Case
244944 - accept with Insufficient Buffer Can Panic (mfg), Overwrite Memory
244950 - yyerror in ftpd.c Does Not Check For Null strchr Return
244990 - versionlog Contents Can Cause TCP Alt Disk Delta To Abort
244993 - getpeername Does Not Return Peer Address for a dgram sockmod Socket
244997 - rexecd Needs to Be BSD Sockets Based to Sync Up with reshd
245011 - getsockname Can Sometimes Fail with EINVAL for Unbound UNIX Socket
245022 - netmask for Loopback Interfaces in Default ifaddrs file Is Not Consistent
245064 - Panics Related to Stale/Closing /dev/ttyA* referenced TCP streams
245067 - gethostbyname() Does Not Handle Numeric Addresses Correctly
245120 - xntpd Misspells umask
245127 - ntptrace Example Hard to Read Because of Formatting Error
245136 - eng2 ktlog message - TCP: rt_msg1: Unsupported Address Family:0:0
245190 - Non-clone Open of UDP Can Cause System Panic
245299 - Ensure Multicast Flag Is Set for Ethernet Devices Only
245300 - Missing "()"s in mail.local man page
245311 - Possible Memory Corruption in socreate()
245381 - Max Value for setsockopt SO_LINGER = 32767, Should Be 65535
245399 - rexecd Does Not Log a Warning/Error on Exits
245444 - CP Clusters Needs Entry in /etc/services
245460 - Bug in icmp_error() Leads to Memory Corruption(std)/Panic(mfg)
245477 - ptx/TCP Must Automatically Be Installed Whenever DYNIX/ptx Is
245515 - Multicast UDP Packets Sent Do Not Use the Interface Address Set by IP_MULTICAST_IF
245519 - timed Does Not Have INADDR_ANY Time - Sometimes!
245539 - Incorporate PDC Components Into ptx/TCP
245551 - UDP/TCP Do Not Work Correctly When Packet Contains IP Options
245555 - routed in ripv2_out Responds to RIP1 Messages
245557 - routed Responds with Valid Metric Even for Non-existent Routes
245559 - Changing Interface Metric Is Not Reflected In Routes Advertised
245561 - routed Does Not Support "trust_gateway" Parameter
245573 - After a Multicast send, Subsequent UDP Packets Sent to Wrong MAC Address
245626 - rlogind Authentication Problem
245690 - routed Should Validate RIP1 Messages for "must-be-zero" Fields
245712 - SIOCATMARK ioctl Fails with 1 Byte OOB in ABI Environment
245742 - ifconfig of ITX/Loop device Returns ioctl (SIOCGIFADDR): Invalid
245840 - ftp - cd Command with user as Argument Causes Problem
245872 - sock_getpeername Should Check for Non-null so->iocsave
245906 - Alignment Error Seen by User from in_pcb.h; Wrong sockaddr Flavor
245944 - ifconfigall Does Not Work if an Interface Name Contains the Other
245993 - Warning Messages in ktlog from Token Ring Interfaces
246088 - sbag_rprocess() Leaks sbappendaddr mblks on 0-length Datagrams
246219 - rarpd Expects Every Device in /dev/net to understand DLPI
246259 - mib2agt Does Not Handle IP Aliases for Interfaces - Dumps Core
246335 - Error Return from getsock/peername ENOMEM; xpg4e Needs ENOBUFS
246519 - ifconfigall Loses Flags Parameter
246551 - tcpdump Filter Does Not Work for Ethernet Configured with SNAP
246662 - tcpdump May Dump Core If gethostbyaddr() Takes More Than 20 Seconds
246706 - named Exits If There Is an Unsupported Option in the Configuration File
246707 - Please Report True BIND Source Version in VERSION String
246800 - netstat returns devnum Not Name, Confusing ifconfigall and Cluster
246873 - Panic in in_open_clone()
246908 - routed Uses Bogus Gateway for Intrinsic Routes
247020 - route -a Should Translate to route fill
247031 - netstat Returns Bogus Information for Multiple Interface Config
247364 - routed Byte Order Problem (Again)
247408 - route Tries RTM_CHANGE Where Our Kernel Canot
247483 - FUNC route -q Option Does Not Work
247546 - WT_ENTRY_RELE Chokes on NULL rt_node Passed by rtentry_remove
247553 - Non-positive User Count Still a Problem in rtentry_validate_cache
247573 - Too Many syslog Messages in EES Log
247589 - timed Bitten by Another Un-initialized Variable (lft_shift)
247592 - attaching_ifaddr May Give Wrong Answer on ifaddr Searches
247635 - named Still Does Not See Aliases (PR#243873 Fix Is Incomplete)
247641 - We Lost the Fix for PR#237010: Cannot Read root-owned .rhosts File
247732 - hosts.equiv Man Page Needs to Specify "+" Feature Support
247733 - STREAMS ioctl on a BSD Raw Socket Panics the Kernel
247829 - Sendmail Denial of Service Vulnerability in 8.8.5
247891 - Panic in rtalloc1 If wte_to_rt() Returns NULL
248229 - FUNC ifconfigall Confused by pe6 and pe60 in ifnets/ifaddrs
248282 - TLI UDP Streams Are Denied the Pleasure of ICMP Error Messages
248283 - SYS: inetd, Fails to Close Accepted File Descriptors and Runs Out
248485 - STREAMS Wars Episode One: The Phantom Data
248521 - p_lock Timeout in solock()
248544 - SYS Possible Time-of-day Clock Shift Message During Stress Run
248927 - ifconfigall (deleting All Interfaces) Causing Panic in rt_newaddr
249518 - SYS: select() Call in resh Hardcoded to 16 - Hangs If More File Descriptors