Once I have created that, I added 676 to the ‘in’ filter, after which we can also see the WriteResponses:Īlso check out the details about the filter syntax and the reference of the opcua filter. We found out that the ServiceNodeId is 673 for the WriteRequest. If you wish to filter WriteRequests, you can find that from the available service list. This is useful, since the log gets easily filled with Read messages, due to the clients typically monitoring the connection and ServerStatus with frequent calls. Use the Expression editor to build your own filter. You can further filter by the port number, etc. If you filter with “opcua”, you will only get OPC UA packets.Īs you can see, it can parse the UA packets down to every parameter for display in the log! You can then just start capturing packets. You must define the port numbers that may contain UA traffic in order to make the opcua protocol filter to work. Once you have started it for the first time, go to Edit-Preferences-Protocols-OpcUa. Click on the CAPTURE FILTERS and enter the filter name and Filter string or directly input the filter string you know in the box. There is one important setting that you need to take care of. Click on CAPTURE, INTERFACES options and choose the Network adapter from drop down menu which will be used to capture running packets in the network on the PC. It can be a valuable tool, if you need to investigate what traffic is going between an UA client and server by revealing the contents of every packet – unless of course, you have enabled encryption on the connection!
It contains several pre-defined filters for various protocols – and yes, also for OPC UA! Wireshark is a great tool for sniffing network traffic. UPDATED: to reflect the current Wireshark version.
0 kommentar(er)
