Long delay opening tshark on CentOS 7

asked 2021-11-10 19:33:03 +0000

bupkes gravatar image

updated 2021-11-11 20:53:25 +0000

An strace shows tshark timing out on this one interface. It doesn't matter which interface I am actually trying to capture on. I do not ever use the USB interfaces. TShark 1.10.14

8171  09:24:34 open("/dev/bus/usb/001/003", O_RDWR) = 6
8171  09:24:34 ioctl(6, USBDEVFS_CONTROL, 0x7ffe3d482280) = -1 ETIMEDOUT (Connection timed out)
8171  09:24:39 close(6)                 = 0

This happens in the middle of all interfaces being enumerated. The problematic usb interface is associated with the virtual IPMI presence. Is it necessary to query the unused interfaces?

# lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

UPDATE: It didn't occur to me that a fully updated CentOS 7 system would be on such an old Wireshark version. I will retest on newer version ASAP.

edit retag flag offensive close merge delete

Comments

Not at all helpful, but 1.10.14 is long obsolete (EOL 2015) and no longer supported by the Wireshark project.


Are you providing tshark with an interface to capture on with a -i parameter?

grahamb gravatar imagegrahamb ( 2021-11-11 09:51:08 +0000 )edit

The joys of using a long-lived distro.

grahamb gravatar imagegrahamb ( 2021-11-11 21:51:45 +0000 )edit

What does tshark --version print?

Guy Harris gravatar imageGuy Harris ( 2021-11-12 07:05:17 +0000 )edit