You can check for well matched hardware at . Wireshark timestamps are presently not carried out in our wrapper library, but it’s deliberate on our TODO. Next releases will include that option. Regarding b and c lamentably this isn’t a Wireshark nor Acrylic related issue.
The hassle depends upon the NDIS interface implementation of some manufacturers. Despite they’re WHQL certified by Microsoft, many of these NDIS implementations are broken or no less than not fully compliant when using track mode. That’s the explanation why RSSIs are always 0 to your device some brands have only values of 100, 50 or 0, as an instance. Same with FCS. Our driver request NDIS interface to come frames with the distinct FCS configuration and is the company driver accountability to ascertain if FCS is accurate or not. However, some driver implementations do not return those four FCS bytes, or they return rubbish as a substitute.
