
llc1(7D) Devices SunOS 5.5
The broadcast address value is the broadcast address returned from the lower
level driver.
Once in theDL_ATTACHED state, the user must send a DL_BIND_REQ to associate a par-
ticular Service Access Point (SAP) with the stream. The llc1 driver interprets the sap field
within theDL_BIND_REQ as an IEEE 802.2 “SAP,” therefore valid values for the sap field
are in the [0-0xFF] range with only even values being legal.
The llc1 driver DLSAP address format consists of the 6-octet physical (e.g., Ethernet)
address component followed immediately by the 1-octet sap (type) component produc-
ing a 7-octet DLSAP address. Applications should not hard-code 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 lengthcan be computed by subtracting the absolute value of the sap
length from the full DLSAP address length or by issuing theDL_PHYS_ADDR_REQ to
obtain the current physical address associated with the stream.
Once in theDL_BOUND state, the user may transmit frames on the LAN by sending
DL_UNITDATA_REQ messages to the llc1 driver. The llc1 driver will route received
frames up all open and bound streams havinga sap which matches the IEEE 802.2 DSAP
as DL_UNITDATA_IND messages. Received frames are duplicated and routed up multi-
ple 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.
In addition to the mandatory, connectionless DLPI message set, the driver additionally
supports the following primitives:
The DL_ENABMULTI_REQ andDL_DISABMULTI_REQ primitives enable/disable recep-
tion of specific multicast group addresses. A set of multicast addresses may be iteratively
created and modified on a per-stream basis using these primitives. These primitives are
accepted by the driver in any driver state that is valid while still being attached to the
ppa.
The DL_PHYS_ADDR_REQ primitive returns the 6-octet physical address currently associ-
ated (attached) to the stream in theDL_PHYS_ADDR_ACK primitive. This primitive is
valid only in states following a successful DL_ATTACH_REQ.
The DL_SET_PHYS_ADDR_REQ primitive changesthe 6-octet physical address currently
associated (attached) to this stream. Once changed, all streams subsequently opened and
attached to this device will obtain this new physical address. Once changed, the physical
address will remain set until this primitive is used to change the physical address again
or the system is rebooted, whichever occurs first.
The DL_XID_REQ/DL_TEST_REQ primitives provide the means for a user to issue an LLC
XID
or TEST request message. A response to one of these messages will be in the form of
a DL_XID_CON/DL_TEST_CON message.
The DL_XID_RES/DL_TEST_RES primitives provide a way for the user to respond to the
receipt of an XID or TEST message that was received as aDL_XID_IND/DL_TEST_IND
message.
7D-192 modified 15 Oct 1993
Comentarios a estos manuales