Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

de(4) [bsd man page]

DE(4)							     Kernel Interfaces Manual							     DE(4)

NAME
de - DEC DEUNA 10 Mb/s Ethernet interface SYNOPSIS
/sys/conf/SYSTEM: NDE de_controllers # DEUNA DESCRIPTION
The de interface provides access to a 10 Mb/s Ethernet network through a Digital Equipment UNIBUS Network Adapter (DEUNA). Each of the host's network addresses is specified at boot time with an SIOCSIFADDR ioctl. The de interface employs the address resolution protocol described in arp(4P) 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 nego- tiated with ARP. This negotiation may be disabled, on a per-interface basis, by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl. DIAGNOSTICS
de%d: hardware address %s. This is a normal autoconfiguration message noting the 6 byte physical ethernet address of the adapter. de%d: oerror, flags=%b tdrerr=%b (len=%d). The hardware indicated an error in transmitting a packet to the cable. The status and error flags are reported. de%d: ierror, flags=%b lenerr=%b (len=%d). The hardware indicated an error in reading a packet from the cable. The status and error flags are reported. de%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was dropped. de%d: buffer unavailable. The interface received more packets than it had buffers allocated to receive them. de%d: address change failed, csr0=%b csr1=%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 following messages indicate a probable hardware error performing the indicated operation during autoconfiguration or initialization. The two control and status registers should indicate the nature of the failure. See the hardware manual for details. de%d: reset failed, csr0=%b csr1=%b. de%d: ppcb failed, csr0=%b csr1=%b. de%d: read addr failed, csr0=%b csr1=%b. de%d: wtring failed, csr0=%b csr1=%b. de%d: wtmode failed, csr0=%b csr1=%b. SEE ALSO
intro(4N), inet(4F), arp(4P) 3rd Berkeley Distribution August 20, 1987 DE(4)

Check Out this Related 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)
Man Page