From: Florian Westphal <fw@strlen.de>
To: Korodev <korodev@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Timestamps, NFLOG, and ULOG
Date: Fri, 22 May 2020 01:26:26 +0200 [thread overview]
Message-ID: <20200521232626.GA26949@breakpoint.cc> (raw)
In-Reply-To: <CAKOsuLo6wdEXEdb9gEbnXhU9uEoFvaWS1SKjaUitm9SaRyz17Q@mail.gmail.com>
Korodev <korodev@gmail.com> wrote:
> Additionally if I implement any sort of queuing or thresholding, which
> I'd like to eventually, the timestamps are affected. This seems to
> indicate I'm not getting the actual packet timestamps. Any ideas on
> what could be causing this or is this expected behaviour?
Its expected. If you want rx timestamps you should set
SO_TIMESTAMP(NS) socket option,
next prev parent reply other threads:[~2020-05-21 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 18:44 Timestamps, NFLOG, and ULOG Korodev
2020-05-21 23:26 ` Florian Westphal [this message]
2020-05-21 23:58 ` Korodev
2020-05-22 0:21 ` Florian Westphal
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=20200521232626.GA26949@breakpoint.cc \
--to=fw@strlen.de \
--cc=korodev@gmail.com \
--cc=netfilter@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.