Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: whireshark cann't detect interfaces..

  1. #1
    Join Date
    Jun 2008
    Beans
    2

    whireshark cann't detect interfaces..

    Hi,

    I installed Wireshark and it starts ok, but cann't find any capture interface ?!? .. any suggestion .. or info ?

    thanks

  2. #2
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Beans
    1,393
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: whireshark cann't detect interfaces..

    You need to start it with root privileges.

    ALT + F2
    gksudo wireshark
    Last edited by Monicker; June 8th, 2008 at 02:28 PM.

  3. #3
    Join Date
    Jul 2006
    Location
    Australia
    Beans
    356
    Distro
    Ubuntu UNR

    Re: whireshark cann't detect interfaces..

    Ahh I wondered why I couldn't see anything eariler myself.

  4. #4
    Join Date
    Jun 2008
    Beans
    2

    Re: whireshark cann't detect interfaces..

    Thanks, that's it. When I started it with "gksudo wireshark", dialog appeared "...Running as user "root" and group "root". This could be dangerous...."
    -> OK and Whireshark detected and showed interfaces but when I klick start button for capturing, whireshark goes dimmed i.e 'not responding' ... only Force Quit helps ...

    Since I installed Ubuntu yesterday I am new to this OS ... maybe I try to do things like on XP without knowing enough about the OS ... at least I didn't crashed so far ..

  5. #5
    Join Date
    Feb 2007
    Beans
    39

    Re: whireshark cann't detect interfaces..

    same thing happens to me. I try to capture an interface and the program stops responding. Any help would be appreciated!

  6. #6
    Join Date
    Aug 2007
    Beans
    27

    Re: whireshark cann't detect interfaces..

    Same here...

    Interface is locked after pressing the "Options" button next to the etho interface.

  7. #7
    Join Date
    Jun 2008
    Beans
    21

    Re: whireshark cann't detect interfaces..

    same problem here also .. looks like a bug ..

  8. #8
    Join Date
    Aug 2007
    Beans
    6

    Re: whireshark cann't detect interfaces..

    Hi to all
    Definitly it seems there is a bug, maybe in gksu(do), maybe in wireshark
    puting gksu (or gksudo) in front of the command in the menu enables the interface selection, but upon chosing one, wireshark hangs, not only that, if you run gksu wireshark, or gksudo wireshark in a terminal, same thing happens.
    But if you open the root terminal in applications / System, and type wireshark, it runs smoothly. Since is not advisable to leave a root terminal open, type wireshark &, it launch wireshark, and releases the terminal so you can quit it

    Carlos Pacheco

  9. #9
    Join Date
    Feb 2010
    Beans
    2

    Re: whireshark cann't detect interfaces..

    Hi, Jus downloaded Wireshark from the repositories. Not bringing up any interfaces at all, even though using the sudo command or running it through the terminal.

    Running it through terminal gets me this message:
    airbeagle@airbeagle-desktop:~$ wireshark
    dumpcap: There are no interfaces on which a capture can be done

    Im in a cisco ccna class and trying to get wireshark to run to work with it a little bit. Running Karmic Koala and Wireshark 1.2.2. I am not good at checking forums so if you can email me directly at air_beagle@yahoo.com that would be very helpful. Thank you very much!

  10. #10
    Join Date
    Jul 2008
    Location
    Alabama, USA
    Beans
    906
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: whireshark cann't detect interfaces..

    Quote Originally Posted by chuky View Post
    Hi to all
    Definitly it seems there is a bug, maybe in gksu(do), maybe in wireshark
    puting gksu (or gksudo) in front of the command in the menu enables the interface selection, but upon chosing one, wireshark hangs, not only that, if you run gksu wireshark, or gksudo wireshark in a terminal, same thing happens.
    But if you open the root terminal in applications / System, and type wireshark, it runs smoothly. Since is not advisable to leave a root terminal open, type wireshark &, it launch wireshark, and releases the terminal so you can quit it

    Carlos Pacheco
    Sounds like it's something to do with environment variables.

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •