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 1292056

Summary:	Use -Q instead of -P to set capture direction
Product:	Red Hat Enterprise Linux 7	Reporter:	Jaroslav Aster <jaster>
Component:	tcpdump	Assignee:	Martin Sehnoutka <msehnout>
Status:	CLOSED ERRATA	QA Contact:	Jaroslav Aster <jaster>
Severity:	medium	Docs Contact:	Vladimír Slávik <vslavik>
Priority:	medium
Version:	7.4	CC:	msehnout, msekleta, thozza
Target Milestone:	rc	Keywords:	FastFix, Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tcpdump-4.5.1-6.el7	Doc Type:	Release Note
Doc Text:	The option to set capture direction for tcpdump changed from "-P" to "-Q" Previously, the tcpdump utility in Red Hat Enterprise Linux used the "-P" option to set the capture direction, while the upstream version used "-Q". The "-Q" option has been implemented and is now preferred. The "-P" option retains the previous function as an alias of "-Q", but displays a warning.	Story Points:	---
Clone Of:	1292055	Environment:
Last Closed:	2017-08-01 12:13:36 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:	1380362

Description Jaroslav Aster 2015-12-16 11:05:55 UTC

The same issue on rhel-7. Tested on tcpdump-4.5.1-3.el7.

+++ This bug was initially created as a clone of Bug #1292055 +++

Description of problem:

In tcpdump-4.0.0-5.20090921gitdf3cb4.2.el6 new option -P was introduced (bug 1099701), but upstream uses -Q option for the same thing, so there is difference between RHEL and upstream. RHEL should use the same option as upstream.

--- Additional comment from Jaroslav Aster on 2015-12-16 06:03:31 EST ---

I suggest to save backward compatibility and use -P as an alias for -Q and print some warning when -P is used.

Comment 5 Jaroslav Aster 2017-04-11 14:45:46 UTC

Hi Martin,

could you please confirm to me that setting -P/-Q is not supposed to work on aarch64? Other architectures work fine. Thanks.

tcpdump: nflog: pcap_setdirection() failed: Setting direction is not implemented on this platform

Comment 6 Martin Sehnoutka 2017-04-24 12:04:46 UTC

Yes, it is not supposed to work everywhere as stated here:
http://www.tcpdump.org/manpages/pcap_setdirection.3pcap.html

Comment 10 errata-xmlrpc 2017-08-01 12:13:36 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://access.redhat.com/errata/RHSA-2017:1871