This wiki has been migrated to and is now deprecated. Please use that site instead.
Differences between revisions 3 and 4
Revision 3 as of 2005-02-07 22:20:38
Size: 1773
Editor: GuyHarris
Comment: Fill in some additional information.
Revision 4 as of 2005-08-25 19:05:27
Size: 1831
Editor: UlfLamping
Comment: add a link
Deletions are marked like this. Additions are marked like this.
Line 50: Line 50:
 * [ IEEE 802.2 LLC]

Logical Link Control (LLC, IEEE 802.2)

XXX - add a brief LLC description here


XXX - add a brief description of LLC history

Protocol dependencies

LLC can use a number of LAN (and MAN/WAN?) protocols as its transport protocol:

  • ["Ethernet"]: LLC can be used for packets on ["Ethernet"] networks, although many protocols don't use it when running atop Ethernet.
  • ["IEEE 802.11"]: LLC is used for data packets on ["IEEE 802.11"] networks.
  • ["FDDI"]: LLC is used for data packets on ["FDDI"] networks.
  • TokenRing: LLC is used for data packets on TokenRing networks.

Example traffic

XXX - Add example traffic here (as plain text or Ethereal screenshot).


The LLC dissector is fully functional.

Preference Settings

(XXX add links to preference settings affecting how LLC is dissected).

Example capture file

XXX - Add a simple example capture file to the SampleCaptures page and link from here. Keep it short, it's also a good idea to gzip it to make it even smaller, as Ethereal can open gzipped files automatically.

Display Filter

A complete list of LLC display filter fields can be found in the [ display filter reference]

  • Show only the LLC based traffic:


Capture Filter

The way you capture only LLC-based protocols depends on the link-layer type of the network on which you're capturing.

XXX: Ethernet - look for packets with a length field, and maybe worry about IPX-over-raw-802.3; Token Ring, FDDI, and 802.11, check for data packets.


LLC (last edited 2008-04-12 17:51:45 by localhost)