You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I updated npcap from 1.73 to 1.74. Installation and everything else works fine, but the timeval ts struct in the pcap_pkthdr no longer updates with a new timestamp for each packet captured; it just stays at a constant value indefinitely.
To Reproduce
I am using pcap_dispatch() with a handler function whose arguments include the pcap_pkthdr* struct. I have made no other changes to my code which is calling into the pcap API.
Expected behavior
I expected the timestamp behavior in 1.74 to be consistent with previous versions. However, I see there were recent changes to the way timestamps are handled in the release notes. Do I need to do call something explicitly in 1.74 to configure my capture resources to return to the prior behavior?
Yeah, appears to be the same. Sorry for the duplicate issue; I had searched for ‘timestamp’ but only in Open issues, so #668 didn’t show up as it was marked as Closed.
Describe the bug
I updated npcap from 1.73 to 1.74. Installation and everything else works fine, but the timeval ts struct in the pcap_pkthdr no longer updates with a new timestamp for each packet captured; it just stays at a constant value indefinitely.
To Reproduce
I am using pcap_dispatch() with a handler function whose arguments include the pcap_pkthdr* struct. I have made no other changes to my code which is calling into the pcap API.
Expected behavior
I expected the timestamp behavior in 1.74 to be consistent with previous versions. However, I see there were recent changes to the way timestamps are handled in the release notes. Do I need to do call something explicitly in 1.74 to configure my capture resources to return to the prior behavior?
Screenshots
n/a
Diagnostic information
Windows 10 Version 22H2, OS Build 19045.2846
DiagReport attached:
DiagReport-20230425-092655.txt
The text was updated successfully, but these errors were encountered: