From: Ben Magistro <koncept1@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>, quentin@armitage.org.uk
Cc: dev@dpdk.org, ben.magistro@trinitycyber.com
Subject: Re: dumpcap w/ pcapng produces out of order/negative times
Date: Thu, 2 Jun 2022 12:34:08 -0400 [thread overview]
Message-ID: <CAKx8PBhSNV7zKioGBuAFQa3ffj6_soYOr+KEiEzZznCV4CbyTQ@mail.gmail.com> (raw)
In-Reply-To: <20220114081547.2ebce3b2@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
In case others wind up here, the issue described here appears to be
addressed by "libpcapng: fix timestamp wrapping in output files". Thanks
for the patch!
https://patches.dpdk.org/project/dpdk/patch/20220517100115.157888-1-quentin@armitage.org.uk/
On Fri, Jan 14, 2022 at 11:15 AM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Thu, 13 Jan 2022 21:38:06 -0500
> Ben Magistro <koncept1@gmail.com> wrote:
>
> > While utilizing dumpcap with our app, we have observed the captured file
> > producing out of order timestamps to include negative times. We are
> still
> > investigating the root cause but believe it is in lib/pcapng. While
> doing
> > some testing of this issue, this behavior was not observed with pcap. In
> > the attached pcap, there are 5 streams (same curl multiple times a few
> > seconds apart), with streams 1 and 3 showing oddities. Specifically,
> > stream 1 is in the future relative to the packet order and stream 3 has a
> > negative time.
> >
> > Not sure if the pcap file will actual post/attach, if it doesn't will try
> > something.
> >
> > System: CentOS7 + devtoolset 9
> > DPDK: v21.11
>
> The library hast convert from TSC (cpu clock) to nanoseconds since 1/1/1970
> The function pcapng_init computes the offset.
>
[-- Attachment #2: Type: text/html, Size: 1871 bytes --]
prev parent reply other threads:[~2022-06-02 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 2:38 Ben Magistro
2022-01-14 16:15 ` Stephen Hemminger
2022-06-02 16:34 ` Ben Magistro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKx8PBhSNV7zKioGBuAFQa3ffj6_soYOr+KEiEzZznCV4CbyTQ@mail.gmail.com \
--to=koncept1@gmail.com \
--cc=ben.magistro@trinitycyber.com \
--cc=dev@dpdk.org \
--cc=quentin@armitage.org.uk \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).