-
Notifications
You must be signed in to change notification settings - Fork 267
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
Timeval unchanged between captured packets in Example03 #470
Comments
Timestamp comes from PCAP library |
Possibly caused by nmap/npcap#668, upgrade to latest Npcap if that's the case |
The Npcap that was installed on my windows 11 is 1.74. I notice that there
is now a 1.76. I'll try to upgrade it and report back if that solves the
problem.
…On Tue, Aug 8, 2023 at 3:45 AM Ayoub Kaanich ***@***.***> wrote:
Possibly caused by nmap/npcap#668
<nmap/npcap#668>, upgrade to latest Npcap if
that's the case
—
Reply to this email directly, view it on GitHub
<#470 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBZJNEYAOEANDIZIDH3IBILXUIKFHANCNFSM6AAAAAA3IHG22A>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Npcap 1.76 fixes the issue. Thanks.
…On Tue, Aug 8, 2023 at 3:44 AM Ayoub Kaanich ***@***.***> wrote:
Timestamp comes from PCAP library
What Libpcap / Npcap version do you have installed?
—
Reply to this email directly, view it on GitHub
<#470 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBZJNE5YJF7TACOMN3JZXJDXUIKBVANCNFSM6AAAAAA3IHG22A>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running the sample always returns the same time stamp 19:36:25,868, even between invocations. Is it a bug?
The text was updated successfully, but these errors were encountered: