I am using wireshark 1.8.3 (windows 7 64 bit).
Thanks, Elkana B asked 19 Mar '15, 06:23 lkanab |
One Answer:
The fourth word in the subject line of this question, as originally posted, indicates where this should be posted. :-) I.e., if you know it's a bug, file it on the Wireshark Bugzilla so that it can be properly tracked as a bug. answered 19 Mar '15, 23:37 Guy Harris ♦♦ |
Any particular reason working with this outdated Wireshark version? Version 1.12 is the current release branch, while 1.10 is the 'old stable' one. Yours is even older.
The OP should be on a more recent version, but this behavior is still present in 1.10.13 and 1.12.4.