Wireshark-bugs: [Wireshark-bugs] [Bug 11369] "Show packet in new window" resets packet info to T
Comment # 3
on bug 11369
from arthur.yurov@thomsonreuters.com
(In reply to Jeff Morriss from comment #1)
> (In reply to arthur.yurov from comment #0)
> > 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.
>
> Where do you see the Protocol Name and Protocol Info which has changed? In
> the new packet window or in the main window? For only that frame or for all
> frames?
>
> > 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.
>
> Changing the category to Qt UI then.
>
>
> Does this problem still show up in more modern versions (you're on the
> development branch so things are changing rapidly, especially in the Qt UI.
I've posted a side by side view of the Legacy UI and the new UI of what it
looks like when I filter by our protocol name. I also demonstrate in this
screenshot that the details of the packet are still properly displayed, the
only issues exist in the packet info of the header at the top.
The plugin was developed using 1.99.3 branch, and I'm running it in 1.99.8
version of Wireshark (Problem exists since 1.99.3). Do we think creating the
plugin in the latest 1.99.8 branch could make a difference with this UI issue?
You are receiving this mail because:
- You are watching all bug changes.
