All rights reserved.
Redistribution and use in source and binary forms are permitted
provided that the above copyright notice and this paragraph are
duplicated in all such forms and that any documentation,
advertising materials, and other materials related to such
distribution and use acknowledge that the software was developed
by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
@(#)ex.4 6.4 (Berkeley) 02/14/89
Each of the host's network addresses is specified at boot time with an SIOCSIFADDR ioctl. The ex interface employs the address resolution protocol described in arp (4) to dynamically map between Internet and Ethernet addresses on the local network.
The interface normally tries to use a ``trailer'' encapsulation to minimize copying data on input and output. The use of trailers is negotiated with ARP. This negotiation may be disabled, on a per-interface basis, by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl.
ex%d: can't initialize. There was a failure in allocating unibus resources for the device.
ex%d: configuration failed; cc = %x. The hardware indicated an error when trying to initalize itself. The error code returned is described at length in the device Reference Manual.
ex%d: receive error %b. The hardware indicated an error in reading a packet from the cable. Specific Error bits are provided
ex%d: transmit error %b. The hardware indicated an error in transmitting a packet to the cable or an illegally sized packet. Specific Error bits are provided
ex%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was dropped.