Simulators › BACnet/SC Capture Lab
BACnet/SC Capture Lab
BACnet Secure Connect moves BACnet into encrypted TLS connections to a hub. That’s great for security and hard on troubleshooting: most of what you used to read in a capture is now “Application Data”. Learn what an SC connection looks like, what you can still see without keys, how to decrypt with a key log when you have one, and how to find expired certificates, untrusted CAs, firewall drops, TLS inspection, idle timeouts, failover and duplicate VMACs.
- Read the work order
- Work the capture: the connection pattern first, then decrypt if you can
- Make the call: what broke and how you know
Choose a scenario
BACnet/SC in five minutes
- DNS for the hub name in the URI (if it uses a name).
- TCP to the URI’s port (no standard port; 443 is common).
- TLS 1.3: Client Hello (hub name in clear), Server Hello, then everything is encrypted, including both certificates.
- WebSocket upgrade with
Sec-WebSocket-Protocol: hub.bsc.bacnet.org. - Connect-Request / Connect-Accept: the node’s VMAC and device UUID.
- Encapsulated-NPDU: ordinary BACnet inside. Heartbeats keep quiet connections alive.
| What you see | Without a key log | With a key log |
|---|---|---|
| TCP handshake, resets, retransmissions | Yes | Yes |
| Hub name (SNI) in the Client Hello | Yes | Yes |
| Certificates, TLS alerts | No (TLS 1.3 encrypts them) | Yes |
| WebSocket upgrade, BVLC-SC messages, BACnet | No: “Application Data” | Yes |
Key logs come from software hubs and test tools; most controllers can’t write one. So every scenario teaches the pattern you can read without keys first. Background: How BACnet/SC works · Troubleshooting BACnet/SC · SC certificates · Cybersecurity section
Scenarios Learning SC, network path, certificates, hubs and migration
Protocols, method and the IT conversation
BAS Communication: A Field Reference covers BACnet, Wireshark for BAS work and the layer-by-layer method used here. Free reading: Planning a BACnet/SC rollout and Talking to IT about the BAS network.
Work order
The capture window is sized for a laptop or desktop screen. On smaller screens it scrolls sideways.
Training mockup that follows Wireshark 4.4’s layout, menus and display-filter language. Not affiliated with the Wireshark Foundation. Get the real thing free at wireshark.org.
Simulated Windows 11 command prompt and network dialogs. Output follows the real formats; the network behind them is a model of the site drawing.