IL(4) BSD/vax Kernel Interfaces Manual IL(4)NAMEil — Interlan NI1010 10 Mb/s Ethernet interface
device il0 at uba0 csr 164000 vector ilrint ilcint
The il interface provides access to a 10 Mb/s Ethernet network through an
Interlan 1010 or 1010A controller.
Each of the host's network addresses is specified at boot time with an
SIOCSIFADDR ioctl(2). The il interface employs the address resolution
protocol described in arp(4) to dynamically map between Internet and Eth‐
ernet addresses on the local network.
The interface normally tries to use a ``trailer'' encapsulation to mini‐
mize 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.
il%d: input error. The hardware indicated an error in reading a packet
off the cable or an illegally sized packet.
il%d: can't handle af%d. The interface was handed a message with
addresses formatted in an unsuitable address family; the packet was
il%d: setaddr didn't work. The interface was unable to reprogram its
physical ethernet address. This may happen with very early models of the
interface. This facility is used only when the controller is not the
first network interface configured for XNS. The oldest interface tested
(188.8.131.52.1.45) has never failed in this way.
il%d: reset failed, csr=%b.
il%d: status failed, csr=%b.
il%d: hardware diag failed, csr=%b.
il%d: verifying setaddr, csr=%b.
il%d: stray xmit interrupt, csr=%b.
il%d: can't initialize. The above messages indicate a probable hardware
error performing the indicated operation during autoconfiguration or ini‐
tialization. The status field in the control and status register (the
low-order four bits) should indicate the nature of the failure. See the
hardware manual for details.
SEE ALSOnetintro(4), inet(4), arp(4)HISTORY
The il interface appeared in 4.2BSD.
4.2 Berkeley Distribution June 5, 1993 4.2 Berkeley Distribution