First time here? Check out the FAQ!
answered 2018-09-07 07:44:55 +0000
This is indeed a bug in Wireshark, thanks for reporting it. The fix is available here: https://code.wireshark.org/review/c/29454/ and will be backported in all the active branches.