
tr(7D) Devices SunOS 5.5
The token ring broadcast address (C0:00:FF:FF:FF:FF) is also supported.
Once in theDL_ATTACHED state, the user must send a DL_BIND_REQ to associate a par-
ticular Service Access Pointer (SAP) with the stream. The tr 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, of which only even values are legal.
In addition to 802.2 service, a “SNAP mode” is also provided by the driver. In this mode,
sap values in the range [0x5de-0xffff] are used to indicate a request to use “SNAP” mode.
The tr driver DLSAP address format consists of the 6-byte physical token ring address
component followed immediately by the 1 or 2-byte sap component, producing a 7 or 8-
byteDLSAP address. Applications should not hardcode to this particular
implementation-specificDLSAP address format, but should instead use information
returned by theDL_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 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 token ring by sending
DL_UNITDATA_REQ messages to the tr driver. The tr driver will route received token
ring frames up all open and bound streams that have a sap which matches the sap in the
DL_UNITDATA_IND messages. Received token ring 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 and
physical (token ring) components.
tr Primitives In addition to the mandatory connectionlessDLPI message set, the driver also 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 using these primitives. These primi-
tives are accepted by the driver in any state followingDL_ATTACHED.
The DL_PROMISCON_REQ andDL_PROMISCOFF_REQ primitives with the
DL_PROMISC_PHYS flag set in the dl_level field is currently unsupported for this driver.
When used with the DL_PROMISC_SAP flag set, this enables/disablesreception of all sap
values. When used with theDL_PROMISC_MULTI flag set, this enables/disables recep-
tion of all functional addresses. The effect of each is always on a per-stream basis and
independent of the other sap and physical level configurations on this stream or other
streams.
The DL_PHYS_ADDR_REQ primitive returns the 6-octet token ring address currently
associated (attached) to the stream in theDL_PHYS_ADDR_ACK primitive. This primitive
is valid only in states following a successful DL_ATTACH_REQ.
7D-380 modified 15 Oct 1993
Comentários a estes Manuais