projects / unix-history / blame
| Commit | Line | Data |
|---|---|---|
| ffe3c13f C |
1 | .TH VV 4 "27 July 1983" |
| 2 | .UC 4 | |
| 3 | .SH NAME | |
| 4 | vv \- Proteon proNET 10 Megabit ring | |
| 5 | .SH SYNOPSIS | |
| 6 | .B "device vv0 at uba0 csr 161000 vector vvrint vvxint" | |
| 7 | .SH DESCRIPTION | |
| 8 | The | |
| 9 | .I vv | |
| 10 | interface provides access to a 10 Mb/s Proteon proNET ring network. | |
| 11 | .PP | |
| 12 | The network number to which the interface is attached must | |
| 13 | be specified with an SIOCSIFADDR ioctl before data can be | |
| 14 | transmitted or received. | |
| 15 | The host's address is discovered by putting the interface in | |
| 16 | digital loopback mode (not joining the ring) | |
| 17 | and sending a broadcast packet from which the source | |
| 18 | address is extracted. | |
| 19 | the Internet address of the interface would be 128.3.0.24. | |
| 20 | .PP | |
| 21 | The interface software implements error-rate limiting on | |
| 22 | the input side. | |
| 23 | This provides a defense against situations where other hosts | |
| 24 | or interface hardware failures cause a machine to be | |
| 25 | inundated with garbage packets. | |
| 26 | The scheme involves an exponential backoff where the input | |
| 27 | side of the interface is disabled for longer and longer periods. | |
| 28 | In the limiting case, | |
| 29 | the interface is turned on every two minutes or so to see | |
| 30 | if operation can resume. | |
| 31 | .PP | |
| 32 | If the installation is running CTL boards which use the old broadcast | |
| 33 | address of 0 instead of the new address of 0xff, the define OLD_BROADCAST | |
| 34 | should be specified in the driver. | |
| 35 | .PP | |
| 36 | If the installation has a Wirecenter, the define WIRECENTER should | |
| 37 | be specified in the driver. | |
| 38 | .BR N.B. : | |
| 39 | Incorrect definition of WIRECENTER can cause hardware damage. | |
| 40 | .PP | |
| 41 | The interface normally tries to use a ``trailer'' encapsulation | |
| 42 | to minimize copying data on input and output. This may be | |
| 43 | disabled, on a per-interface basis, by setting the IFF_NOTRAILERS | |
| 44 | flag with an SIOCSIFFLAGS ioctl. | |
| 45 | .SH DIAGNOSTICS | |
| 46 | .PP | |
| 47 | \fBvv%d: host %d\fP. The software announces the host | |
| 48 | address discovered during autoconfiguration. | |
| 49 | .PP | |
| 50 | \fBvv%d: can't initialize\fP. The software was unable to | |
| 51 | discover the address of this interface, so it deemed | |
| 52 | "dead" will not be enabled. | |
| 53 | .PP | |
| 54 | \fBvv%d: error vvocsr=%b\fP. The hardware indicated an error on | |
| 55 | the previous transmission. | |
| 56 | .PP | |
| 57 | \fBvv%d: output timeout\fP. The token timer has fired and the | |
| 58 | token will be recreated. | |
| 59 | .PP | |
| 60 | \fBvv%d: error vvicsr=%b\fP. The hardware indicated an error | |
| 61 | in reading a packet off the ring. | |
| 62 | .PP | |
| 63 | \fBen%d: can't handle af%d\fP. The interface was handed | |
| 64 | a message with addresses formatted in an unsuitable address | |
| 65 | family; the packet was dropped. | |
| 66 | .PP | |
| 67 | \fBvv%d: vs_olen=%d\fP. The ring output routine has been | |
| 68 | handed a message with a preposterous length. This results in | |
| 69 | an immediate | |
| 70 | .IR "panic: vs_olen" . | |
| 71 | .SH SEE ALSO | |
| 72 | intro(4N), inet(4F) |