dnet(7d) - osol9

1dnet(7D)                            Devices                           dnet(7D)
2
3
4

NAME

6       dnet - Ethernet driver for DEC 21040, 21041, 21140 Ethernet cards
7

SYNOPSIS

9       /kernel/drv/dnet
10
11

DESCRIPTION

13       The  dnet  Ethernet  driver  is  a  multithreaded,  loadable, clonable,
14       STREAMS GLD driver. Multiple controllers installed  within  the  system
15       are  supported  by  the  driver. The dnet driver functions include con‐
16       troller  initialization,  frame  transmit   and   receive,   functional
17       addresses,  promiscuous  and  multicast support, and error recovery and
18       reporting.
19

APPLICATION PROGRAMMING INTERFACE

21       The cloning character-special device, /dev/dnet, is used to access  all
22       DEC 21040/21041/21140 devices installed in the system.
23
24
25       The  dnet  driver  is  dependent on /kernel/misc/gld, a loadable kernel
26       module that provides the dnet driver with the DLPI  and  STREAMS  func‐
27       tionality  required  of  a LAN driver.  See gld(7D) for more details on
28       the primitives supported by the driver.
29
30
31       The device is  initialized  on  the  first  attach  and  de-initialized
32       (stopped) on the last detach.
33
34
35       The  values  returned  by  the  driver  in the DL_INFO_ACK primitive in
36       response to a DL_INFO_REQ from the user are as follows:
37
38           o      The maximum SDU is 1500 (ETHERMTU - defined  in  <sys/ether‐
39                  net.h>).
40
41           o      The minimum SDU is 0.
42
43           o      The DLSAP address length is 8.
44
45           o      The MAC type is DL_ETHER.
46
47           o      The  sap  length  value  is −2, meaning the physical address
48                  component is followed immediately by a 2-byte sap  component
49                  within the DLSAP address.
50
51           o      The  broadcast  address value is the Ethernet/IEEE broadcast
52                  address (FF:FF:FF:FF:FF:FF).
53
54
55       Once in the DL_ATTACHED state, the user must send a DL_BIND_REQ to  as‐
56       sociate a particular Service Access Point (SAP) with the stream.
57

PRECONFIGURATION

59       The  PCI configuration process varies from system to system. Follow the
60       instructions provided by the vendor.
61
62   Known Problems and Limitations
63           o      On multiport cards (exception: Osicom  (Rockwell)  RNS2340),
64                  the  first port is the top port. (On the Osicom RNS2340, the
65                  first port is the bottom port.)
66
67           o      If the  dnet driver fails to determine the correct speed and
68                  duplex  mode  resulting  in  a corresponding drop in perfor‐
69                  mance, set the speed and duplex  mode  using  the  dnet.conf
70                  file.
71
72           o      The  dnet  driver incorrectly counts carrier lost or no car‐
73                  rier errors while in full-duplex mode. There is  no  carrier
74                  signal present when in full-duplex mode and it should not be
75                  counted as an error.
76
77           o      Version 4 SROM formats are not supported.
78

CONFIGURATION

80       The /kernel/drv/dnet.conf file supports the following options:
81
82       full-duplex    For full duplex operation use  full-duplex=1,  for  half
83                      duplex  use  full-duplex=0.  Half-duplex operation gives
84                      better results on older 10mbit networks.
85
86
87       speed          For 10mbit operation use speed=10, for 100mbit operation
88                      use speed=100. Certain 21140 based cards will operate at
89                      either speed. Use the speed  property  to  override  the
90                      100mbit default in this case.
91
92

FILES

94       /dev/dnet                character special device
95
96
97       /kernel/drv/dnet.conf    dnet configuration file
98
99

ATTRIBUTES

101       See attributes(5) for descriptions of the following attributes:
102
103
104
105
106       ┌─────────────────────────────┬─────────────────────────────┐
107       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
108       ├─────────────────────────────┼─────────────────────────────┤
109       │Architecture                 │x86                          │
110       └─────────────────────────────┴─────────────────────────────┘
111