Public bug reported:
Binary package hint: tcpdump
tcpdump takes an unusually long time to display packets in Ubuntu Jaunty
(3.9.8-4ubuntu2), whereas it works find under my Ubuntu Intrepid (3.9.8-4)
setup; packets are shown instantly.
Wireshark displays packets instantly in both cases.
This is true of all and "-i any" interfaces I test.
The packet times are correct, but it can take between 5 and 10 seconds
for packets to be shown, regardless of packet type, source, destination
or interface. CPU utilisation does not increase during this time.
The following is a short excerpt running on the "any" interface with the
filter "ip proto \\icmp". I have used pings for simplicity here.
Filtering the packets does not speed up the display. The network nor
the computer are busy while testing.
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
64 bytes from 192.168.0.3: icmp_seq=1 ttl=255 time=10.4 ms
08:38:40.450249 IP 192.168.0.12 > 192.168.0.3: ICMP echo request, id 62810, seq
1, length 64
08:38:40.450273 IP 192.168.0.12 > 192.168.0.3: ICMP echo request, id 62810, seq
1, length 64
08:38:40.452587 IP 192.168.0.3 > 192.168.0.12: ICMP echo reply, id 62810, seq
1, length 64
As you can see, the ICMP_ECHO_REQUEST is sent twice for each ping. I'm not
sure if this is normal, or even related.
Pinging 127.0.0.1 only sends the request once before receiving the reply, but
tcpdump still takes its time to show the captured packets.
This certainly makes tcpdump difficult to use for real-time capture.
** Affects: tcpdump (Ubuntu)
Importance: Undecided
Status: New
** Tags: jaunty regression tcpdump ubuntu
--
tcpdump takes an unusually long time to display packets (Jaunty)
https://bugs.launchpad.net/bugs/423570
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
