Bug 1025841
Summary: | Unable to filter packets by VLAN tag | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Norman Elton <normelton> |
Component: | libpcap | Assignee: | Michal Sekletar <msekleta> |
Status: | CLOSED ERRATA | QA Contact: | Tomas Dolezal <todoleza> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4 | CC: | emajorsi, msekleta, psklenar |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | libpcap-1.4.0-4.20130826git2dbcaa1.el6 | Doc Type: | Bug Fix |
Doc Text: |
Documentation for this issue is the same as for #1063328
Previously, running the "tcpdump" command with the filter expressioncontaining the keyword "vlan" produced unexpected output, as the filtergenerated by the libpcap Berkeley Packet Filter (BPF) compiler did notemploy BPF extensions. To fix this bug, libpcap has been amended and nowgenerates filters that use BPF extensions when appropriate. As a result,running "tcpdump" with filters containing "vlan" produces correct results.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-07-22 06:17:12 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: | 1070830, 1159820 |
Description
Norman Elton
2013-11-01 17:41:39 UTC
This is not a bug in tcpdump itself but rather in libpcap. Reassigning there. Note that before doing something about this on libpcap side, some changes in kernel has to be introduced. Just an quick update on the current status. Kernel part is done, now we can move to fixing libpcap. Opened a pull request on github trying to address this. https://github.com/the-tcpdump-group/libpcap/pull/391 Feel free to join the discussion on github and also testing would be much appreciated. Thanks. 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-1288.html |