Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1
Fixed In:
14.1.0, 12.1.4.1
Opened: Oct 31, 2013 Severity: 4-Minor Related Article:
K43726131
Although packets are flowing correctly through the BIG-IP system, the tcpdump utility may capture no packets when certain command options are used.
The tcpdump utility does not capture any packets, which may create confusion for a BIG-IP Administrator performing troubleshooting on the system. This issue does not affect the traffic-passing abilities of the system, however.
This issue occurs when all of the following conditions are met: - You configure tcpdump to listen for packets on a physical interface (e.g., -i 1.1). - You configure tcpdump to save the packets to a file in binary format (e.g., -w /var/tmp/example.pcap). - You configure tcpdump to produce verbose output while capturing packets (e.g., -v, -vv or -vvv).
You can work around this issue by starting the tcpdump utility without the -v, -vv or -vvv verbose output options.
None