From: Pablo Neira Ayuso <pablo@netfilter.org>
To: ravin goyal <ravirocks1021@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: libnetfilter_conntrack's NFCT_OF_TIMESTAMP is not working
Date: Tue, 15 Mar 2016 12:12:14 +0100 [thread overview]
Message-ID: <20160315111214.GA2122@salvia> (raw)
In-Reply-To: <CANU0Mn2nE6nR-v_K8wMmEV4LQx5_GrS1Ea3_--yBLdYSLKEYDw@mail.gmail.com>
On Tue, Mar 15, 2016 at 04:21:38PM +0530, ravin goyal wrote:
> Hi
>
> Thanks for the reply, I ran same command conntrack -E -o ktimestamp
> and results are same as you have shown
> but when i ran conntrack -E -otimestamp OR conntrack -E
> -otimestamp,extended , start and stop timestamp are missing in the
> output.
-o timestamp displays the timestamp at the beginning of the line:
[1458039983.184296] [UPDATE] udp 17 180 src=10.10.10.132 dst=8.8.8.8 sport=36310 dport=53 ...
[1458040055.867546] [DESTROY] udp 17 ... delta-time=180
and the delta-time when the entry is destroyed.
> Can you please explain how -o ktimestamp and -otimestamp,extended
> differ in output ??
-o ktimestamp relies on the in-kernel timestamp when you search for
more precision.
-o timestamp is a userspace timestamp.
The 'extended' options, from manpage says:
conntrack -L -o extended
Show the connection tracking table in /proc/net/nf_conntrack format
This basically appends the layer 3 protocol at the beginning of the
line.
Please, send me patches to update conntrack(8) manpage if you believe
this information is not available there. Thanks.
next prev parent reply other threads:[~2016-03-15 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 6:34 libnetfilter_conntrack's NFCT_OF_TIMESTAMP is not working ravin goyal
2016-03-15 10:19 ` Pablo Neira Ayuso
[not found] ` <CANU0Mn2nE6nR-v_K8wMmEV4LQx5_GrS1Ea3_--yBLdYSLKEYDw@mail.gmail.com>
2016-03-15 11:12 ` Pablo Neira Ayuso [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-14 5:09 ravin goyal
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=20160315111214.GA2122@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=ravirocks1021@gmail.com \
/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).