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
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 Yes, it is not supposed to work everywhere as stated here: http://www.tcpdump.org/manpages/pcap_setdirection.3pcap.html 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 |