Technical data

SunOS 5.5 Devices pe(7D)
No optional quality of service (QOS) support is included at present, so the
QOS fields are 0.
The provider style is DL_STYLE2.
The version is DL_VERSION_2.
The broadcast address value is Ethernet/IEEE broadcast address
(FF:FF:FF:FF:FF:FF).
Once in the DL_ATTACHED state, the user must send a DL_BIND_REQ to associate a
particular SAP (Service Access Pointer) with the stream. The pe driver interprets the sap
field within the DL_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.
In addition to Ethernet V2 service, an “802.3 mode” is provided by the driver and works
as follows. sap values in the range [0-1500] are treated as equivalent and represent a
desire by the user for “802.3” mode. If the value of the sap field of the DL_BIND_REQ is
within this range, then the driver computes the length, not including initial M_PROTO
mblk, of all subsequent DL_UNITDATA_REQ messages and transmits 802.3 frames hav-
ing this value in the MAC frame header length field. All frames received from the media
having a “type” field in this range are assumed to be 802.3 frames and are routed up all
open streams that are bound to any sap value within this range. If more than one stream
is in “802.3 mode,” then the frame will be duplicated and routed up multiple streams as
DL_UNITDATA_IND messages.
The pe 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-
byte DLSAP address. Applications should not hardcode to this particular
implementation-specific DLSAP address format but use information returned in 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 physical address associated with the stream.
Once in the DL_BOUND state, the user may transmit frames on the Ethernet by sending
DL_UNITDATA_REQ messages to the pe driver. The pe driver will route received Eth-
ernet frames up all those open and bound streams having a sap which matches the Ether-
net type as DL_UNITDATA_INDmessages. Received Ethernet frames are duplicated
and routed up multiple open streams if necessary. The DLSAP address contained within
the DL_UNITDATA_REQ and DL_UNITDATA_IND messages consists of both the sap
(type) and physical (Ethernet) components.
PE Primitives In addition to the mandatory connectionlessDLPI message set, the driver additionally
supports the primitives discussed below.
The DL_ENABMULTI_REQ and DL_DISABMULTI_REQ primitives enable/disable
reception of individual multicast group addresses. A set of multicast addresses may be
iteratively created and modified on a per-stream basis using these primitives. These
modified 20 Dec 1993 7D-253