 | 1 | initial version |
This seems to be a bug in the 3.0 series of Wireshark. You could consider filing a bug report, but since the 3.0 series will become End-of-Life in a few months I don't know if this is going to be solved. Why not upgrade to the 3.2 series (3.2.2 at the moment)? This doesn't seem to exhibit this behaviour.
