| Bug ID |
11369
|
| Summary |
"Show packet in new window" resets packet info to TCP
|
| Product |
Wireshark
|
| Version |
1.99.x (Experimental)
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.99.7 (v1.99.7-0-g03c02f3 from master)
Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 (64-bit) with Qt 5.3.1, with WinPcap (unknown), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, without PortAudio,
with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, without
WinPcap, with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7-3740QM CPU @ 2.70GHz (with SSE4.2), with 8062MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 31101
--
I am developing a dissector plugin to decode our company's wire-format for
development and debugging purposes. The dissector properly decodes and displays
information for the ports that the plugin automatically decodes as our
protocol, however when I use "Show Packet In New Window" it will reset the
Protocol Name and Protocol Info back to TCP while still displaying our decoded
information in the packet's payload as we click through the different packets
that contain our data.
If I use "Decode As" at this point to attempt to set the port manually back to
our protocol, the packet information will blink to our protocol for a second,
then back to TCP with TCP information (Again, while still displaying our
decoded protocol in the payload data).
Please note: This only happens when using the new interface (Wireshark.exe).
The legacy interface (Wireshark-gtk.exe) works perfectly.
I'm unsure of the proper way to debug this problem, and have not been able to
find similar issues with others. Has this been run into before, and are there
any tips I can get? Any information that I can give to help solve this issue?
The plugin is written in C.
Thanks!
You are receiving this mail because:
- You are watching all bug changes.