Technical data

SunOS 5.5 Devices be(7D)
The broadcast address value is Ethernet/IEEE broadcast address
(0xFFFFFFFF).
When in the DL_ATTACHED state, the user must send aDL_BIND_REQ to associate a par-
ticular SAP (Service Access Point) with the Stream. The be driver interprets the sap field
within theDL_BIND_REQ as an Ethernet “type”; therefore, valid values for the sap field
are in the [0-0xFFFF] range. Only one Ethernet type can be bound to the Stream at any
time.
10/100 Mbit/s algorithm for auto-selection is to be determined.
If the user selects a sap with a value of 0, the receiver will be in 802.3 mode. All frames
received from the media having a “type” field in the range [0-1500] are assumed to be
802.3 frames and are routed up all open Streams which are bound to sap value 0. If more
than one Stream is in “802.3 mode” then the frame will be duplicated and routed up mul-
tiple Streams as DL_UNITDATA_IND messages.
In transmission, the driver checks thesap field of the DL_BIND_REQ if the sap value is 0,
and if the destination type field is in the range [0-1500]. If either is true, the driver com-
putes the lengthof the message, not includinginitialM_PROTO mblk (message block), of
all subsequentDL_UNITDATA_REQ messages and transmits 802.3 frames that have this
value in the MAC frame header length field.
The driver also supports raw M_DATA mode. When the user sends a DLIOCRAW ioctl,
the particular Stream is put in raw mode. A complete frame along with a proper ether
header is expected as part of the data.
The be driver DLSAP address format consists of the 6-byte physical (Ethernet) address
component followed immediately by the 2-byte sap (type) component producing an 8-
byteDLSAP address. Applications should not hardcode to this particular
implementation-specificDLSAP address format but use information returned by the
DL_INFO_ACK primitive to compose and decompose DLSAP addresses. The sap length,
full DLSAP length, and sap/physical ordering are included within the DL_INFO_ACK.
The physical address length can be computed by subtracting the sap length from the full
DLSAP address length or by issuing the DL_PHYS_ADDR_REQ to obtain the current phy-
sical address associated with the Stream.
When in the DL_BOUND state, the user may transmit frames on the Fast Ethernetby
sendingDL_UNITDATA_REQ messages to the be driver. The be driver routes received
Fast Ethernet frames as DL_UNITDATA_IND messages up all the open and bound
Streams that have sap matching the Fast Ethernet type. Received Fast Ethernet frames are
duplicated and routed up multiple open Streams if necessary. TheDLSAP address con-
tained within the DL_UNITDATA_REQ and DL_UNITDATA_IND messages consists of
both the sap (type) and physical (Fast Ethernet) components.
be Primitives In addition to the mandatory connectionlessDLPI message set the driver additionally
supports the following primitives.
The DL_ENABMULTI_REQ andDL_DISABMULTI_REQ primitives enable/disable recep-
tion of individual multicast group addresses. A set of multicast addresses may be itera-
tively created and modified on a per-stream basis with these primitives. Theseprimitives
modified 26 Jan 1994 7D-41