Wireshark-bugs: [Wireshark-bugs] [Bug 8529] tshark does not decode field icmp.resp_in while Wire
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 27 Mar 2013 12:57:48 +0000

changed bug 8529

What Removed Added
Status UNCONFIRMED CONFIRMED
CC   eapache@gmail.com
Ever confirmed   1

Comment # 1 on bug 8529 from 
This is a known behaviour and has to do with a few oddities of the way the
dissection engine is called from wireshark vs from tshark (you are correct that
it has to do with the fact that resp_in is a 'future-dependent' field).

We're still trying to figure out what the best way to implement/fix this is,
there have been a few long discussions on the mailing list already.

Most recent one starts at:
https://www.wireshark.org/lists/wireshark-dev/201303/msg00008.html

If the larger problem ends up with a master bug this one will likely end up
marked as a duplicate of it. Until then I'm afraid there isn't much of a
workaround, sorry. Just use wireshark where possible.

Evan

You are receiving this mail because:
  • You are watching all bug changes.