Wireshark-bugs: [Wireshark-bugs] [Bug 5935] New: Capturing doesn't work in Wireshark
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 19 May 2011 10:31:02 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5935

           Summary: Capturing doesn't work in Wireshark
           Product: Wireshark
           Version: SVN
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Blocker
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: guy@xxxxxxxxxxxx


Build Information:
wireshark 1.7.0 (SVN Rev 37297 from /trunk)

Copyright 1998-2011 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GTK+ 2.12.11, with GLib 2.16.4, with libpcap 1.0.0, with
libz 1.2.3, without POSIX capabilities, without libpcre, with SMI 0.4.8,
without
c-ares, without ADNS, with Lua 5.1, without Python, with GnuTLS 2.6.0, with
Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Dec
20 2009 14:19:53), without AirPcap.

Running on Mac OS 10.6.7 (Darwin 10.7.0), with libpcap version 1.0.0, with libz
1.2.3, GnuTLS 2.6.0, Gcrypt 1.4.5.

Built using gcc 4.2.1 (Apple Inc. build 5666) (dot 3).

--
If I try to capture on, for example, en1, Wireshark runs dumpcap without any -i
arguments.

The current state of the capture code in the trunk is very much Not Ready For
Prime Time; for one thing, the capture_options structure has both an iface
member and an ifaces member, with the GUI setting the former and the code that
runs dumpcap only using the latter.

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