Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1045601

Summary:	Allow tcpdump to support libpcap nanosecond timestamping
Product:	Red Hat Enterprise Linux 6	Reporter:	Dave Sullivan <dsulliva>
Component:	tcpdump	Assignee:	Michal Sekletar <msekleta>
Status:	CLOSED ERRATA	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:	Eva Majorsinova <emajorsi>
Priority:	medium
Version:	6.5	CC:	amelicha, ebenes, hartsjc, kdube, msekleta
Target Milestone:	beta	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tcpdump-4.0.0-5.20090921gitdf3cb4.2.el6	Doc Type:	Enhancement
Doc Text:	tcpdump supports -J, -j, and --time-stamp-precision options As kernel, glibc, and libpcap now provide APIs to obtain nanosecond resolutions timestamps, tcpdump has been updated to leverage this functionality. Users can now query which timestamp sources are available (-J), set a specific timestamp source (-j), and request timestamps with a specified resolution (--time-stamp-precision).	Story Points:	---
Clone Of:
Clones:	1151406 (view as bug list)		Environment:
Last Closed:	2015-07-22 06:19:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	994246, 1075802, 1095797, 1159820, 1159926

Description Dave Sullivan 2013-12-20 20:10:13 UTC

Description of problem:

Need tcpdump to support new libpcap nanosecond timestamping

libpcap now supports nanonsecond timestamps via BZ below

https://bugzilla.redhat.com/show_bug.cgi?id=916749 

At [1] you can find tcpdump built against libpcap containing high precision timestamp patches. Please note -P switch and also switches -j/-J.

[1] http://msekleta.fedorapeople.org/

Comment 2 Michal Sekletar 2014-05-15 08:31:02 UTC

I sent patches for this upstream and topic is discussed here [0]. Should be merged soonish.

Comment 3 Michal Sekletar 2014-05-15 08:33:21 UTC

Arghh...Link to the upstream discussion.

[0] https://github.com/the-tcpdump-group/tcpdump/pull/377

Comment 9 Michal Sekletar 2015-02-03 10:02:44 UTC

http://pkgs.devel.redhat.com/cgit/rpms/tcpdump/commit/?h=rhel-6.7&id=9a37001a7e527c3883d1c2a0fb90cd8a71a3bfad -> MODIFIED

Comment 13 errata-xmlrpc 2015-07-22 06:19:59 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1294.html