|
|
1.1 root 1: .\" Copyright (c) 1983 Regents of the University of California.
2: .\" All rights reserved. The Berkeley software License Agreement
3: .\" specifies the terms and conditions for redistribution.
4: .\"
5: .\" @(#)dmc.4 6.4 (Berkeley) 1/30/87
6: .\"
7: .TH DMC 4 "January 30, 1987"
8: .UC 5
9: .SH NAME
10: dmc \- DEC DMC-11/DMR-11 point-to-point communications device
11: .SH SYNOPSIS
12: .B "device dmc0 at uba0 csr 167600 vector dmcrint dmcxint"
13: .SH DESCRIPTION
14: The
15: .I dmc
16: interface provides access to a point-to-point communications
17: device which runs at either 1 Mb/s or 56 Kb/s. DMC-11's communicate
18: using the DEC DDCMP link layer protocol.
19: .PP
20: The
21: .I dmc
22: interface driver also supports a DEC DMR-11 providing point-to-point
23: communication running at data rates from 2.4 Kb/s to 1 Mb/s.
24: DMR-11's are a more recent design and thus are preferred over DMC-11's.
25: The NXMT and NRCV constants in the driver may be increased in this case,
26: as the DMR can accept up to 64 transmit and receive buffers, as opposed
27: to 7 for the DMC.
28: .PP
29: The configuration flags specify how to set up the device,
30: .br
31: 0 -- full duplex DDCMP (normal mode)
32: .br
33: 1 -- DDCMP Maintence mode (generally useless)
34: .br
35: 2 -- DDCMP Half Duplex, primary station
36: .br
37: 3 -- DDCMP Half Duplex, secondary station
38: .ti
39: .PP
40: Several device error counters are available via "adb", for
41: more information see the adb script /usr/lib/adb/dmcstats, or the
42: DMC11 technical manual.
43: .PP
44: The host's address must be specified with an SIOCSIFADDR ioctl,
45: and the destination address specified with a SIOCSIFDSTADDR ioctl,
46: before the interface will transmit or receive any packets.
47: .SH ROUTING
48: The driver places a HOST entry in the kernel routing tables for the
49: address given in the SIOCSIFDSTADDR ioctl. To use the DMC as a
50: link between local nets, the route to the remote net must be added manually
51: with the
52: .IR route (8)
53: command, or by the use of the routing process
54: .IR routed (8)
55: on each end of the link.
56: .SH DIAGNOSTICS
57: .BR "dmc%d: bad control %o" .
58: A bad parameter was passed to the
59: .I dmcload
60: routine.
61: .PP
62: .BR "dmc%d: unknown address type %d" .
63: An input packet was received which contained a type of
64: address unknown to the driver.
65: .PP
66: .BR "DMC fatal error 0%o" .
67: A fatal error in DDMCP occurred, causing the device to be restarted.
68: .PP
69: .BR "DMC soft error 0%o" .
70: A non-fatal error in DDMCP has occurred.
71: .PP
72: .BR "dmc%d: af%d not supported" .
73: The interface was handed a message which has
74: addresses formatted in an unsuitable address family.
75: .SH SEE ALSO
76: intro(4N), inet(4F)
77: .SH BUGS
78: The current version of the driver uses a link-level encapsulation
79: so that multiple protocol types may be used.
80: It is thus incompatible with earlier drivers,
81: including the 4.2BSD version.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.