
Using the Technician Interface to Configure and Run Packet Capture
B-53
00000020: 00 00 00 00 00 00 00 00 aa aa 03 00 80 c2 00 0e
00000030: 00 00 00 00 00 80 00 00 00 a3 00 00 0c 00 00 00
X.25
The X.25 protocol currently does not have a special data link filter offset. If you
configure a data link filter, set the offset to 0. The data link filter works the same
way that the MAC filter works. The X.25 protocol uses the hardware’s link layer
capabilities. This means that Packet Capture receives only the frame’s Layer 3
(packet layer) data.
An example of a hexadecimal display of an X.25 packet follows:
Pkt# 8 04/26/94 09:00:42.103 X25 47 Rx
00000000: 10 01 e2 00 00 00 00 00 01 00 00 00 00 00 02 00
00000010: 1e aa aa 03 00 00 a2 80 ff 00 00 a2 02 c9 b6 00
00000020: 00 a2 02 c9 b6 81 02 01 01 00 00 00 00 00 38 10
Token Ring
The Token Ring physical media has a data link filter offset of 14 bytes plus the
RIF (routing information field) field, if a RIF is present. This places the data link
filter point at the DSAP (destination service access point) byte. Packet Capture
receives only LLC frames from the Token Ring. It does not receive the Access
Control and Frame Control bytes at the beginning of each packet. Packet Capture
inserts the hexadecimal value 1040 at the beginning of each packet for
compatibility and possible future use.
An example of a hexadecimal display of a Token Ring frame follows:
Pkt# 10 04/18/94 12:58:58.885 TOKEN 52 Rx
00000000: 10 40 c0 00 00 00 01 00 00 00 c5 00 00 30 42 42
00000010: 03 00 00 00 00 00 80 00 00 00 a3 00 00 0c 00 00
00000020: 00 00 80 00 00 00 a3 00 00 0c 80 06 00 00 14 00
00000030: 02 00 0f 00 00 00 00 00 00 00 00 00 00 00 00 00
Komentarze do niniejszej Instrukcji