Bug ID 657727: Running tcpdump from TMSH cannot capture the local "tmm" interface

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 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, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Apr 10, 2017
Severity: 3-Major
Related Article:
K39694060

Symptoms

Cannot run tcpdump against the "tmm" interface. System posts errors similar to the following: tcpdump: pcap_loop: Device /Common/tmm not found tcpdump: ioctl: No such device This occurs because the 'tmm0' interface was renamed to 'tmm' beginning in v12.1.0, but the libbigpacket conditional logic to handle "special device names" still references 'tmm0'.

Impact

Cannot run tcpdump on the 'tmm' internal interface.

Conditions

-- When running tmsh, an environment variable ("TMOS_PATH") is set. -- The user logs in to the CLI with a default shell of tmsh (either as configured, or with a role assigned via remote-roles), or tries to run tcpdump via tmsh.

Workaround

Unset the 'TMOS_PATH' environment variable before running tcpdump.

Fix Information

None

Behavior Change