Listen to this Post

Introduction:
A frozen production line with 21 controllers and a crashed HMI led to an unexpected discovery: an obscure Ethernet feature called PAUSE frames (IEEE 802.3x) was the culprit. This case study reveals how a single unmanaged switch and a malfunctioning device can halt an entire industrial network—and what you can do to prevent it.
Learning Objectives:
- Understand how Ethernet PAUSE frames work and their potential risks
- Learn how unmanaged switches can become single points of failure
- Discover best practices for hardening industrial networks against similar failures
1. What Are Ethernet PAUSE Frames?
PAUSE frames are part of the IEEE 802.3x standard, allowing a device to request a temporary halt in Ethernet traffic to prevent buffer overflows.
Command to Check PAUSE Frame Support (Linux):
ethtool -a eth0 | grep -i pause
What This Does:
- Checks if PAUSE frames are enabled on the specified interface (
eth0). - Output will show `RX` (receive) and `TX` (transmit) pause frame status.
Mitigation:
- Disable PAUSE frames if unnecessary:
ethtool -A eth0 rx off tx off
- How a Crashed HMI Triggered a Network-Wide Freeze
The HMI’s Ethernet card, still receiving traffic post-crash, sent PAUSE frames to the switch, which then propagated them to all connected controllers.
- How a Crashed HMI Triggered a Network-Wide Freeze
Windows Command to Check Network Adapter Status:
Get-NetAdapter | Select-Object Name, Status, LinkSpeed
What This Does:
- Lists all network adapters and their current state.
- Helps identify if a device is malfunctioning.
- The Danger of Unmanaged Switches in Industrial Networks
Unmanaged switches lack configuration options, making them vulnerable to buffer bloat and cascading failures.
- The Danger of Unmanaged Switches in Industrial Networks
Alternative: Use Managed Switches with Flow Control Disabled
Cisco Example:
switch(config) interface GigabitEthernet0/1 switch(config-if) flowcontrol receive off switch(config-if) flowcontrol send off
What This Does:
- Disables PAUSE frames on a per-port basis.
- Prevents buffer exhaustion from a single faulty device.
4. Diagnosing Switch Buffer Overflows
If a switch’s memory fills due to PAUSE frames, it may stop forwarding traffic entirely.
Linux Command to Monitor Switch Buffer Usage (SNMP):
snmpwalk -v 2c -c public <switch_IP> 1.3.6.1.2.1.31.1.1.1
What This Does:
- Retrieves interface statistics, including buffer utilization.
- Helps identify congestion points.
5. Preventing Production Network Failures
Best practices to avoid similar incidents:
- Replace Unmanaged Switches – Use managed switches with QoS and flow control settings.
- Isolate Critical Traffic – VLANs or separate physical networks for HMIs and controllers.
- Monitor PAUSE Frames – Use network taps or SPAN ports to detect abnormal pauses.
Wireshark Filter for PAUSE Frames:
[/bash]
eth.type == 0x8808
[bash]
What This Does:
– Captures only PAUSE frames for analysis.
What Undercode Say:
– Key Takeaway 1: PAUSE frames, while useful for congestion control, can cause system-wide failures if misconfigured or left unchecked.
– Key Takeaway 2: Unmanaged switches in industrial environments are a liability—upgrade to managed switches with granular flow control.
Analysis:
This incident highlights how legacy Ethernet features, combined with outdated hardware, can disrupt critical operations. Modern networks should enforce strict traffic policies, segment critical systems, and actively monitor for abnormal behavior.
Prediction:
As Industrial IoT (IIoT) expands, similar issues will emerge in smart factories. Proactive network hardening—disabling obsolete protocols, deploying AI-driven anomaly detection, and replacing unmanaged hardware—will be essential to prevent costly downtimes.
For further reading on PAUSE frames, visit: https://lnkd.in/e4TW4FPQ
🎯Let’s Practice For Free:
IT/Security Reporter URL:
Reported By: Rob Hulsebos – Hackers Feeds
Extra Hub: Undercode MoN
Basic Verification: Pass ✅


