Bug 331211 - Latest captured packet does not appear on the list while capturing
Summary: Latest captured packet does not appear on the list while capturing
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: wireshark
Version: 7
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Radek Vokál
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-14 07:16 UTC by Juha Leppänen
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-10-15 07:31:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Juha Leppänen 2007-10-14 07:16:38 UTC
Description of problem:

Wireshark does not show the last packet captured on the packet list.
For example if someone sends an UDP NetrSendMessenger packet and my
PC sends back a ICMP reject packet, only the received UDP packet is shown
right away. When the next packet is captured, even minutes later,
the previous sent ICMP reject packet is shown, with the correct time
so I assume it was sent immediately after the UDP packet was received.
But again the latest packet just captured does not appear on the list.
When stopping capture, the latest captured packet appears on list.

Version-Release number of selected component (if applicable):
0.99.6

How reproducible:
Always.

Steps to Reproduce:
1. Start wireshark, give root password.
2. Start capturing, with "not arp" as capture option. 
3.
  
Actual results:

Latest captured packet not shown on the list.

Expected results:

List of captured packets should be uptodate.

Additional info:

I noticed also that yum-updatesd leaves connections
to mirrors in CLOSE_WAIT state for hours, with 1 byte in Recv-Queue
for each connection. I don't know if this has nothing to do
with the problem with wireshark ... ?

Comment 1 Juha Leppänen 2007-10-14 07:38:32 UTC
Better Summary: "Wireshark - List of captured packets missing the latest one"

Comment 2 Radek Vokál 2007-10-15 07:31:21 UTC
This is known bug which seems to be fixed in latest upstream built. See comments
in http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1181

I'm closing this bug as Fixed UPSTREAM, will appear in next version of wireshark.


Note You need to log in before you can comment on or make changes to this bug.