> There is a similar problem in the hexdump window. If you capture, say, a > UDP packet, click on the "+ User Datagram Protocol" tree item, and match > selected, you get two copies of the hexdump. Looks like the hexdump > display isnt cleared before it is updated. Version 0.7.1. This may be a consequence of the fact that, in 0.7[.x], applying a display filter (which "Follow TCP Stream" and "Match Selected" do) attempts to re-select the currently selected packet if it's matched by the display filter; the re-selection has code to clear the hex dump, but, apparently, it's not managing to clear it....
Powered by MHonArc 2.6.10