BACnet, the ASHRAE building automation and control networking protocol, has been designed specifically to meet the communication needs of building automation and control systems for applications such as heating, ventilating, and air-conditioning control, lighting control, access control, and fire detection systems. The BACnet protocol provides mechanisms by which computerized equipment of arbitrary function may exchange information, regardless of the particular building service it performs. As a result, the BACnet protocol may be used by head-end computers, general-purpose direct digital controllers, and application specific or unitary controllers with equal effect.
XXX - add a brief description of PROTO history
- ["TCP"]: Typically, BACnet uses ["TCP"] as its transport protocol. The well known TCP port for BACnet traffic is 47808.
XXX - Add example decoded traffic for this protocol here (as plain text or Wireshark screenshot).
The PROTO dissector is (fully functional, partially functional, not existing, ... whatever the current state is). Also add info of additional Wireshark features where appropriate, like special statistics of this protocol.
(XXX add links to preference settings affecting how PROTO is dissected).
Example capture file
XXX - Add a simple example capture file to the SampleCaptures page and link from here (see below). Keep this file short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.
A complete list of PROTO display filter fields can be found in the [http://www.wireshark.org/docs/dfref/protofirstletter/proto.html display filter reference]
Show only the PROTO based traffic:
You cannot directly filter PROTO protocols while capturing. However, if you know the ["TCP"] port used (see above), you can filter on that one.
Capture only the PROTO traffic over the default port (80):
tcp port 80
- add link to PROTO specification and where to find additional info on the web about it, e.g.:
[http://www.ietf.org/rfc/rfc123.txt RFC 123] The RFC title - explanation of the RFC content.