usr/share/man/cat4/vax/il.0

IL(4)             BSD Programmer's Manual (VAX Architecture)             IL(4)

N\bNA\bAM\bME\bE
     i\bil\bl - Interlan NI1010 10 Mb/s Ethernet interface

S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
     d\bde\bev\bvi\bic\bce\be i\bil\bl0\b0 a\bat\bt u\bub\bba\ba0\b0 c\bcs\bsr\br 1\b16\b64\b40\b00\b00\b0 v\bve\bec\bct\bto\bor\br i\bil\blr\bri\bin\bnt\bt i\bil\blc\bci\bin\bnt\bt

D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
     The i\bil\bl 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 i\bil\bl 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.

D\bDI\bIA\bAG\bGN\bNO\bOS\bST\bTI\bIC\bCS\bS
     i\bil\bl%\b%d\bd:\b: i\bin\bnp\bpu\but\bt e\ber\brr\bro\bor\br.\b.  The hardware indicated an error in reading a packet
     off the cable or an illegally sized packet.

     i\bil\bl%\b%d\bd:\b: c\bca\ban\bn'\b't\bt h\bha\ban\bnd\bdl\ble\be a\baf\bf%\b%d\bd.\b.  The interface was handed a message with ad-
     dresses formatted in an unsuitable address family; the packet was
     dropped.

     i\bil\bl%\b%d\bd:\b: s\bse\bet\bta\bad\bdd\bdr\br d\bdi\bid\bdn\bn'\b't\bt w\bwo\bor\brk\bk.\b.  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
     (2.7.1.0.1.45) has never failed in this way.

     i\bil\bl%\b%d\bd:\b: r\bre\bes\bse\bet\bt f\bfa\bai\bil\ble\bed\bd,\b, c\bcs\bsr\br=\b=%\b%b\bb.\b.
     i\bil\bl%\b%d\bd:\b: s\bst\bta\bat\btu\bus\bs f\bfa\bai\bil\ble\bed\bd,\b, c\bcs\bsr\br=\b=%\b%b\bb.\b.
     i\bil\bl%\b%d\bd:\b: h\bha\bar\brd\bdw\bwa\bar\bre\be d\bdi\bia\bag\bg f\bfa\bai\bil\ble\bed\bd,\b, c\bcs\bsr\br=\b=%\b%b\bb.\b.
     i\bil\bl%\b%d\bd:\b: v\bve\ber\bri\bif\bfy\byi\bin\bng\bg s\bse\bet\bta\bad\bdd\bdr\br,\b, c\bcs\bsr\br=\b=%\b%b\bb.\b.
     i\bil\bl%\b%d\bd:\b: s\bst\btr\bra\bay\by x\bxm\bmi\bit\bt i\bin\bnt\bte\ber\brr\bru\bup\bpt\bt,\b, c\bcs\bsr\br=\b=%\b%b\bb.\b.
     i\bil\bl%\b%d\bd:\b: c\bca\ban\bn'\b't\bt i\bin\bni\bit\bti\bia\bal\bli\biz\bze\be.\b.  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.

S\bSE\bEE\bE A\bAL\bLS\bSO\bO
     netintro(4),  inet(4),  arp(4)

H\bHI\bIS\bST\bTO\bOR\bRY\bY
     The i\bil\bl interface appeared in 4.2BSD.

4.2 Berkeley Distribution        June 5, 1993                                1