forked from osmocom/wireshark
![]() Also use $(top_builddir) instead of ../../ in a couple of other spots. svn path=/trunk/; revision=25863 |
||
---|---|---|
.. | ||
AUTHORS | ||
ChangeLog | ||
COPYING | ||
Doxyfile | ||
Makefile.am | ||
Makefile.common | ||
Makefile.nmake | ||
moduleinfo.h | ||
moduleinfo.nmake | ||
opcua.c | ||
opcua_application_layer.c | ||
opcua_application_layer.h | ||
opcua_complextypeparser.c | ||
opcua_complextypeparser.h | ||
opcua_enumparser.c | ||
opcua_enumparser.h | ||
opcua_hfindeces.c | ||
opcua_hfindeces.h | ||
opcua_identifiers.h | ||
opcua_security_layer.c | ||
opcua_security_layer.h | ||
opcua_serviceparser.c | ||
opcua_serviceparser.h | ||
opcua_servicetable.c | ||
opcua_simpletypes.c | ||
opcua_simpletypes.h | ||
opcua_transport_layer.c | ||
opcua_transport_layer.h | ||
plugin.rc.in | ||
README |
OpcUa Plugin: ============= This plugin implements the dissection of the OpcUa Binary Protocol. Author: Gerhard Gappmeier ascolab GmbH http://www.ascolab.com Overview: ========= OpcUa (OPC Unified Architecture) is a vendor and platform independent protocol for automation technology. It is the successor of the COM/DCOM based specifications OPC DA, OPC Alarm & Events, OPC HDA, etc. It unifies all this technologies into a single protocol. The specification describes abstract services that are independent of the underlying protocol. For now there exist protocol mappings to a Binary TCP based protocol and a SOAP based Webservice. Also a hybrid version will be available where the Binary messages are transported by a single webservice command called "Invoke". More information about the technology you can find on http://www.ascolab.com/index.php?file=ua&lang=en. Protocol Mappings: ================== Binary (TCP): The fastest and most flexible version (small footprint, no XML and SOAP necessary) can easily be tunneled (SSH, IPSEC, etc.), redirected, ... SOAP version: Easy to implement with verious tools like .Net, JAVA, gSOAP, etc. Better to communicate through firewalls via HTTP. SOAP with Binary Attchment: Combines the advantages of both. The messages are encoded as Binary, and transported via SOAP as binary attachment. The OPC Foundation offers a free Opc Ua stack implementation in ANSI C for all members. This stack implements the binary protocol as well as the SOAP version. It's easily portable to different kinds of operating systems from embedded devices to servers. This makes it easy to implement Opc Ua applications based on this stack and it is expected that the binary protocol will be the most used protocol. Nevertheless it's free to everbody to implement an own stack according to the specification. An own implementation of the SOAP version should be easy with the various SOAP toolkits. For more information see http://www.opcfoundation.org Known limitations: ================== * In this version the security layer contains only dummy data. The plugin decodes the transport layer, skips the security dummy data and decodes the application layer. Security implementation will follow when it has been implemented in the Opc Ua stack.