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.

Sign up for GitHub

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

Jump to bottom

Npcap 1.74 - timestamps incorrect, fixed as system boot time #668

Closed
gbloice opened this issue Apr 24, 2023 · 1 comment
Closed

Npcap 1.74 - timestamps incorrect, fixed as system boot time #668

gbloice opened this issue Apr 24, 2023 · 1 comment

Comments

@gbloice
Copy link
Contributor

gbloice commented Apr 24, 2023 •
edited

Describe the bug

When capturing traffic from any interface (I tried Ethernet and Loopback) the timestamp for all packets appears to be the system boot time.

To Reproduce
Steps to reproduce the behavior:

  1. Using Wireshark (4.0.5) with npcap 1.74, perform capture
  2. Inspect timestamps
  3. Note timestamps for all packets are identical and appear to be system boot time.
  4. Switch Wireshark view to File Format
  5. Inspect packet block data
  6. Note timestamps are identical for all packets as in 3. above.

Expected behavior
The timestamps in packets should reflect reality.

Diagnostic information

  • Windows version: Windows 10 22H2 19045.2846
  • Output of DiagReport: Attached.

DiagReport-20230424-111401.txt
@gbloice gbloice changed the title Npcap 1.7.4 - timestamps incorrect, fixed as system boot time Npcap 1.74 - timestamps incorrect, fixed as system boot time Apr 24, 2023
@dmiller-nmap
Copy link
Contributor

Thanks, I can verify this is happening. Somehow this isn't in our regression tests, so I'll add it and get a fix out.

geraldcombs pushed a commit to wireshark/wireshark that referenced this issue Apr 24, 2023
@pquantin
Revert "Windows: upgrade Npcap to 1.74"
b47dd4a 
This reverts commit 8b55d7c.

Let's revert due to nmap/npcap#668
@bubbasnmp bubbasnmp mentioned this issue Apr 25, 2023
Closed
@kayoub5 kayoub5 mentioned this issue Aug 8, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gbloice @dmiller-nmap