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 4569] Trying to Run Wireshark as "root" causes system to completely lockup (requires hard reset)

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


From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 11 Mar 2010 23:03:59 -0800 (PST)

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4569

--- Comment #6 from Jaap Keuter <jaap.keuter@xxxxxxxxx> 2010-03-12 08:03:45 CET ---
(In reply to comment #4)
> (In reply to comment #2)
> > What do
> > 
> >     tcpdump -D
> >     dumpcap -D
> >     dumpcap -S
> > 
> > show?
> 
> tcpdump -D doesn't show anything.  It simply puts me back to the command line.
> Both "dumpcap" messages provide the message "dumpcap: There are no interfaces
> on which a capture can be done".

You've got to run them as root.

> Also, in reply to Comment #1, I did run "dumpcap" using "sudo dumpcap -i eth0
> -c 10".  It then counted to 10 in short order (I was downloading a web page),
> and stopped.  It did not freeze or cause any problems.

Cool, basic capture on Ethernet works, so now lets look for the failing
interfaces.

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

  • References:
    • [Wireshark-bugs] [Bug 4569] New: Trying to Run Wireshark as "root" causes system to completely lockup (requires hard reset)
      • From: bugzilla-daemon
  • Prev by Date: [Wireshark-bugs] [Bug 4569] Trying to Run Wireshark as "root" causes system to completely lockup (requires hard reset)
  • Next by Date: [Wireshark-bugs] [Bug 4569] Trying to Run Wireshark as "root" causes system to completely lockup (requires hard reset)
  • Previous by thread: [Wireshark-bugs] [Bug 4569] Trying to Run Wireshark as "root" causes system to completely lockup (requires hard reset)
  • Next by thread: [Wireshark-bugs] [Bug 4569] Trying to Run Wireshark as "root" causes system to completely lockup (requires hard reset)
  • Index(es):
    • Date
    • Thread

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