Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

packet timestamp in pcap_pkthdr broken after updating from v1.73 to v1.74 #671

Closed
njk42 opened this issue Apr 25, 2023 · 3 comments
Closed

Comments

@njk42
Copy link

njk42 commented Apr 25, 2023

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

@bubbasnmp
Copy link

Duplicate of #668 ?

@njk42
Copy link
Author

njk42 commented Apr 25, 2023

Duplicate of #668 ?

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.

@dmiller-nmap
Copy link
Contributor

Duplicate of #668

@dmiller-nmap dmiller-nmap marked this as a duplicate of #668 Apr 27, 2023
@dmiller-nmap dmiller-nmap closed this as not planned Won't fix, can't repro, duplicate, stale Apr 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants