Skip to main content
net10.0net8.0net9.0

OPC UA PubSub diagnostics: capture, dissection (incl. encrypted UADP) and replay of UDP / MQTT PubSub traffic.

Published
Oct 12, 2026
8d ago
Total Downloads
260
260

Install

dotnet add package OPCFoundation.NetStandard.Opc.Ua.PubSub.Diagnostics --version 2.0.1
ProductVersions
.NET
net10.0net8.0net9.0

README

OPCFoundation.NetStandard.Opc.Ua.PubSub.Diagnostics

Packet-capture, dissection and replay tooling for OPC UA PubSub (Part 14) traffic. Captures the raw NetworkMessages exchanged over the UDP datagram and MQTT broker transports, writes them to .pcap / .pcapng for Wireshark, and dissects them back into structured DataSets — including decryption of encrypted UADP messages when the matching security keys are available (from a captured key log or a live Security Key Service).

What it does

  • Capture PubSub frames in-process via a zero-cost, opt-in tap on the Opc.Ua.PubSub.Udp / Opc.Ua.PubSub.Mqtt transports, or off the wire from a network interface.
  • Dissect captured UADP and JSON NetworkMessages into DataSetMessages / DataSets, reusing the standard PubSub decoders.
  • Decrypt encrypted UADP NetworkMessages (PubSub-Aes128-CTR / PubSub-Aes256-CTR, Part 14 §8.3 / Annex A.2.2.5) by resolving the SecurityTokenId in the UADP SecurityHeader to the matching key.
  • Replay a recorded capture back through the dissection pipeline.

Relationship to Opc.Ua.Core.Diagnostics

This package mirrors the UA-SC capture stack in OPCFoundation.NetStandard.Opc.Ua.Core.Diagnostics and reuses its .pcap / .pcapng writers. PubSub is connectionless and message-secured, so it uses its own frame and key-material abstractions rather than the UA-SC channel/token model.

Target frameworks

net8.0, net9.0, net10.0.

Documentation

See docs/PubSubDiagnostics.md in the UA-.NETStandard repository.

Changes from Previous Version

No structural changes between v2.0.0 and v2.0.1.

Adoption Assessment

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.Compatibility metadata lists 3 target frameworks; confirm the exact target used by your application.The published metadata declares 75 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.