ln(4) [ultrix man page]

ln(4)							     Kernel Interfaces Manual							     ln(4)

Name
       ln - Lance Ethernet interface

Syntax
       device ln0 at ibus? vector lnintr

Description
       The interface provides access to a 10 Mb/s Ethernet network through the Lance controller.

       The  host's  Internet  address  is specified at boot time with an SIOCSIFADDR ioctl.  The interface employs the address resolution protocol
       described in to map dynamically 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.  This	can  be  disabled  for	an
       interface by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl.  Trailers are only used for packets destined for Internet hosts.

       The  SIOCSPHYSADDR ioctl can be used to change the physical address of the Lance.  The SIOCRPHYSADDR ioctl can be used to read the physical
       address of the Lance.

       The SIOCADDMULTI and SIOCDELMULTI ioctls can be used to add or delete multicast addresses.  The Lance recognizes a maximum of 12  multicast
       addresses.

       The  SIOCRDCTRS	and  SIOCRDZCTRS ioctls can be used to read or ``read and clear'' the Ethernet driver counters.  The argument to these two
       ioctls is a pointer to a counter structure, found in

       The SIOCENABLBACK and SIOCDISABLBACK ioctls can be used to enable and disable the interface loopback mode respectively.

Diagnostics
       The diagnostic error messages contain relevant information provided by the Lance.

       ln%d: can't handle af%d
       The interface was handed a message with addresses formated in an unsuitable address family, and the packet was dropped.

       ln%d: memory error (MERR)
       A memory parity error has occurred.

       ln%d: lnalloc: cannot alloc memory ...
       The driver was unable to allocate memory for internal data structures.

       ln%d: initialization error
       The driver was unable to initialize the network interface.

       ln%d: SIOCADDMULTI fail, multicast list full
       Too many multicast requests have been made.

See Also
       arp(4p), inet(4f), intro(4n)

																	     ln(4)

xna(4)							     Kernel Interfaces Manual							    xna(4)

Name
       xna - DEBNI and DEMNA Ethernet interfaces

Syntax
       device xna0 at vaxbi? node? vector xnaintr (DEBNI)
       device xna0 at xmi? node? vector xnaintr (DEMNA)

Description
       The  driver provides access to a 10 Mbytes Ethernet network through the DEBNI and DEMNA adapters.  The DEBNI is an Ethernet to BI bus.  The
       DEMNA is an Ethernet to XMI adapter.

       The host's Internet address is specified at boot time with an SIOCSIFADDR ioctl.  The driver employs the Address  Resolution  Protocol,	as
       described in to map dynamically between Internet and Ethernet addresses on the local network.

       The  driver normally tries to use a trailer encapsulation to minimize copying data on input and output.	This can be disabled for an inter-
       face by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl.  Trailers are used only for packets destined for Internet hosts.

       The SIOCSPHYSADDR ioctl can be used to change the physical address of the adapter and SIOCRPHYSADDR  can  be  used  to  read  its  physical
       address.   SIOCADDMULTI	and  SIOCDELMULTI can be used to add or delete multicast addresses.  The driver supports a maximum of 12 multicast
       addresses. The argument to the latter ioctls is a pointer to an ``ifreq'' structure found in

       SIOCRDCTRS and SIOCRDZCTRS ioctls can be used to read or read and clear network counters. The argument  to  the	latter	two  ioctls  is  a
       pointer to a counter structure ``ctrreq'' found in

       The ioctls SIOCENABLBACK and SIOCDISABLBACK can be used to enable and disable the interface loopback mode.

Restrictions
       The PUP protocol family is not supported.

Diagnostics
       xna%d: port self-test failed:<register list>
       Adapter did not pass the power-up self-test during autoconfiguration time. The port attachment fails.

       xna%d: couldn't allocate...
       The driver was unable to allocate memory for adapter data structures.  The port attachment fails.

       xna%d: port probe failed:<register list>
       The driver was unable to bring the adapter into the initialized state.  The port attachment fails.

       xna%d: port init failed:<register list>
       The driver failed to prepare the adapter for runtime use.

       xna%d: port state changed, resetting:<register list>
       The adapter issued a port state change interrupt. The port state is reset.

       xna%d: port reset failed
       The driver was unable to bring the adapter into the initialized state during a port reset.

       xna%d: command failed, error code:<error code>
       The adapter port command failed. The error code gives reason for failure.

       xna%d: couldn't handle af%d
       A packet with an undefined protocol type has been sent to the adapter.

       xna%d: addmulti failed, multicast list full
       Too many multicast requests have been made.

See Also
       arp(4p), inet(4f), intro(4n)

																	    xna(4)