https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16394
Peter Wu <pe...@lekensteyn.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|IN_PROGRESS |RESOLVED
--- Comment #11 from Peter Wu <pe...@lekensteyn.nl> ---
(In reply to fuwa3-wsh from comment #9)
> > Question for you, was the original capture actually a WireGuard trace? If
> > not, then the heuristics should probably be improved as well.
>
> No, those packets are not Wireguard traffic.
Hm, it looks like the heuristics has to be improved to avoid this. Until then,
you can disable the WireGuard protocol as workaround.
The crash has been fixed in
v3.3.0rc0-574-gb2ee7a2876
v3.2.2rc0-53-g73c5fff899
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
