Hi simon.limkm,
This issue will be correct in a future release, (see this post: Wireshark captures)
Regards