IEEE 802: reading the LAN/MAN standards family

IEEE 802 Ethernet and wireless networking standards

What is IEEE 802? Ethernet, Wi-Fi and network standards

IEEE 802 is a family of standards underlying local and metropolitan area networks. Ethernet, Wi-Fi and network interconnection relate to different parts of that family. There is also an overview and architecture standard, IEEE 802-2024, explaining the family's structure. A catalogue statement saying “IEEE 802 compliant” alone does not identify the supported networking features.

For industrial communication, the practical question is: Which specific standard, physical connection and application protocol are supported? Matching connectors do not establish interoperability.

Commonly encountered IEEE 802 standards

Standard / branchMain subjectPractical relevance
IEEE 802.3 Ethernet MAC and physical layer specifications Ethernet transmission media, link speeds and frame transmission
IEEE 802.11 Wireless LAN MAC and physical layer specifications The technical basis of Wi-Fi technologies
IEEE 802.1Q Bridged networks and VLANs Managed network switches and logical network segmentation
IEEE 802.1X Port-based network access control Managing network access for authenticated devices
IEEE 802.15.4 Low-rate wireless network MAC and physical layer specifications An underlying technology for low-power wireless sensor networks

This table is not a complete list of the IEEE 802 family. Editions and amendments change over time. Procurement should specify the supported features and applicable edition, rather than only the family number.

Are MAC, PHY and IP the same thing?

PHY concerns physical transmission; MAC concerns medium access and frame functions. Common IEEE 802 technologies relate to the OSI model's physical and data link layers. A MAC address differs from an IP address, and an Ethernet frame does not define a complete application's communication rules.

In Modbus TCP, for example, Modbus messages travel over TCP/IP, commonly using Ethernet underneath. An Ethernet interface therefore does not imply Modbus TCP support. Protocols carried over Ethernet and the differences between EtherNet/IP and Modbus TCP help explain this distinction.

How Ethernet relates to industrial Ethernet

PROFINET, EtherNet/IP and EtherCAT are different industrial communication solutions using Ethernet technology. A shared underlying technology does not mean a shared application protocol. Device protocols, roles, data structures and timing requirements must also be compatible.

EtherCAT cyclic process data can travel directly within Ethernet frames, without requiring TCP/IP for that exchange. This is one of the differences between EtherCAT and conventional Ethernet use. IEC 61784 communication profiles and real-time Ethernet profiles provide a separate standards framework for assessing industrial protocols in more detail.

TSN: greater speed or more predictable delivery?

TSN (Time-Sensitive Networking) is a set of standards within IEEE 802 supporting time-sensitive communication. Its purpose goes beyond bandwidth: it addresses bounded latency and reduced packet delay variation. IEEE 802.1AS covers timing and synchronization, while relevant mechanisms within 802.1Q address different aspects of traffic management.

A gigabit link alone does not guarantee real-time performance. Real-time communication performance requires end devices, switches and network configuration to be assessed together. A “TSN supported” claim should identify the supported mechanisms and profile.

VLANs, access control and cybersecurity

A VLAN logically separates network segments through suitable switch configuration. 802.1X supports authentication and authorization for port-based network access. These serve different purposes. Creating a VLAN does not automatically encrypt data. Ethernet network security also requires appropriate access rules, management controls and security mechanisms. IEC 62443 provides a broader cybersecurity framework for industrial systems.

Editor's note — a control cabinet example: Suppose two PLCs have identical RJ45 sockets marked “100 Mbit/s Ethernet”. If one supports only Modbus TCP and the other only EtherNet/IP, connecting the cable does not establish application communication. Check for a shared protocol, then verify device roles and data mapping. Investigate physical connectivity, addressing and application behaviour separately, in that order.

What should you check in a catalogue?

Read the specific standard, physical medium, speed, protocol and required networking features together. If PoE is required, verify suitable support at both the power source and powered device. Assess cable length and installation conditions for the selected Ethernet technology. Interpret “communication port” in context: it may refer to a physical interface or a software port.

Do not treat Modbus RTU as interchangeable with Modbus TCP, or RS-485 as interchangeable with Ethernet. Solutions such as OPC UA address data sharing and interoperability at another level. A sound network choice starts by matching the right layers and functions.

Related topics: Ethernet FAQ  ·  How EtherCAT works  ·  RS-232 / RS-422 / RS-485  ·  Modbus FAQ  ·  OPC UA