static/netbsd/man4/man4.vax/il.4 4.html


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78

<table class="head">
  <tr>
    <td class="head-ltitle">IL(4)</td>
    <td class="head-vol">Device Drivers Manual (vax)</td>
    <td class="head-rtitle">IL(4)</td>
  </tr>
</table>
<div class="manual-text">
<section class="Sh">
<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1>
<p class="Pp"><code class="Nm">il</code> &#x2014; <span class="Nd">Interlan
    NI1010 10 Mb/s Ethernet interface</span></p>
</section>
<section class="Sh">
<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
<p class="Pp"><code class="Cd">il0 at uba0 csr 164000</code></p>
</section>
<section class="Sh">
<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
<p class="Pp">The <code class="Nm">il</code> interface provides access to a 10
    Mb/s Ethernet network through an Interlan 1010 or 1010A controller.</p>
<p class="Pp">Each of the host's network addresses is specified at boot time
    with an <code class="Dv">SIOCSIFADDR</code> <a class="Xr">ioctl(2)</a>. The
    <code class="Nm">il</code> interface employs the address resolution protocol
    described in <a class="Xr">arp(4)</a> to dynamically map between Internet
    and Ethernet addresses on the local network.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1>
<dl class="Bl-diag">
  <dt>il%d: input error.</dt>
  <dd>The hardware indicated an error in reading a packet off the cable or an
      illegally sized packet.</dd>
  <dt>il%d: can't handle af%d.</dt>
  <dd>The interface was handed a message with addresses formatted in an
      unsuitable address family; the packet was dropped.</dd>
  <dt>il%d: setaddr didn't work.</dt>
  <dd>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.</dd>
  <dt>il%d: reset failed, csr=%b.</dt>
  <dd></dd>
  <dt>il%d: status failed, csr=%b.</dt>
  <dd></dd>
  <dt>il%d: hardware diag failed, csr=%b.</dt>
  <dd></dd>
  <dt>il%d: verifying setaddr, csr=%b.</dt>
  <dd></dd>
  <dt>il%d: stray xmit interrupt, csr=%b.</dt>
  <dd></dd>
  <dt>il%d: can't initialize.</dt>
  <dd>The above messages indicate a probable hardware error performing the
      indicated operation during autoconfiguration or initialization. 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.</dd>
</dl>
</section>
<section class="Sh">
<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE
  ALSO</a></h1>
<p class="Pp"><a class="Xr">arp(4)</a>, <a class="Xr">inet(4)</a>,
    <a class="Xr">netintro(4)</a></p>
</section>
<section class="Sh">
<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1>
<p class="Pp">The <code class="Nm">il</code> interface appeared in
    <span class="Ux">4.2BSD</span>.</p>
</section>
</div>
<table class="foot">
  <tr>
    <td class="foot-date">June 5, 1993</td>
    <td class="foot-os">NetBSD 10.1</td>
  </tr>
</table>