DDN(4) (vax)

DDN(4) | Device Drivers Manual (vax) | DDN(4)

# NAME

`ddn` —
DDN Standard Mode X.25 IMP network interface

# SYNOPSIS

`ddn0 at uba0 csr 166740 vector ddnintr`

# DESCRIPTION

NOTE: This driver has not been ported from 4.4BSD yet.

The `ddn` device provides a DDN Standard Mode X.25 interface to an IMP using the ACC ACP625 X.25 board. It is normally used for connecting to the Defense Data Network (DDN). The controller itself is not accessible to users, but instead provides a network interface for the Internet Protocol described in ip(4).

# DIAGNOSTICS

ddn%d: not alive.
  The initialization routine was entered even though the device did not autoconfigure. This indicates a system problem.
ddn%d: failed getting UBA resources for lcn %d."
  Insufficient UNIBUS resources existed to initialize the device. This is likely to be a shortage of UNIBUS mapping registers.
ddn%d: couldn't get X25 init buffer.
  This indicates that an mbuf could not be allocated for sending the initialization message to the ACP625.
DDN: illegal X25 address length!
DDN: illegal X25 address format!
  These errors indicate a problem with the called X.25 address received from the IMP on an incoming call.
X25 RESET on lcn = %d.
  This indicates that an unexpected X.25 RESET was received on the indicated LCN.
X25 INTERRUPT on lcn = %d, code = %d.
  This indicates that an unexpected X.25 INTERRUPT Packet was received on the indicated LCN.
ddn%d: failed to get supr msg bfr!
  This indicates that an mbuf could not be allocated for sending a supervisor message to the ACP625.

Any other error message from ‘`ddn%d:`’ indicates a serious error detected by either the driver or the ACP625 firmware.

# SEE ALSO

ip(4), netintro(4)

# HISTORY

The `ddn` interface appeared in 4.3BSD.

June 5, 1993 | NetBSD 9.5