Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-bugs: [Wireshark-bugs] [Bug 1002] packets only displayed after wireshark has stopped

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 2 Aug 2006 07:58:07 +0000 (GMT)

http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1002





------- Comment #3 from jeff.morriss@xxxxxxxxxxx  2006-08-02 07:58 GMT -------
In that case it would probably be interesting to know if you see the same
behavior using 'tshark' or 'dumpcap'.  That would answer the question:

- is the kernel not sending the packets up?
- (or) is the GUI not displaying them?

I suspect the former which makes this...  A PCAP problem?  Or difficult to
analyze and solve, anyway...


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  • Prev by Date: [Wireshark-bugs] [Bug 1002] packets only displayed after wireshark has stopped
  • Next by Date: [Wireshark-bugs] [Bug 1026] Invalid characters in PDML output when a packet containing "aim.sst.icon" is found (a AOL AIM message)
  • Previous by thread: [Wireshark-bugs] [Bug 1002] packets only displayed after wireshark has stopped
  • Next by thread: [Wireshark-bugs] [Bug 1002] packets only displayed after wireshark has stopped
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation