| Bug ID |
9744
|
| Summary |
OPCUA Filter Doesn't Work
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.5
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
benny.caldwell@gmail.com
|
Created attachment 12548 [details]
OPCUA conversation - not detected by Wireshark
Build Information:
Version 1.10.5 (SVNRev 54262 from /trunk-1.10)
Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (32-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Dec 19 2013), with AirPcap.
Running on 32-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz, with 3325MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
Steps to reproduce:
1) Start a capture on an interface that an OPCUA server is listening on
2) Establish a connection to the OPCUA server from an OPCUA client and read
values of a node
3) The OPCUA conversation is shown in wireshark as TCP protocol
4) Enter "opcua" in the filter box to show packets containing the OPCUA
conversation - none are shown
It seems that Wireshark is not identifying a conversation as OPCUA. A similar
conversation has been observed using the "opcua" filter in previous versions of
Wireshark.
A capture of the OPCUA conversation is attached.
You are receiving this mail because:
- You are watching all bug changes.
