Wireshark-bugs: [Wireshark-bugs] [Bug 1324] New: PacketGetAdapterNames Error when selecting/list
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1324
Summary: PacketGetAdapterNames Error when selecting/listing
interfaces
Product: Wireshark
Version: 0.99.5
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Critical
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: trav.ethereal@xxxxxxxxxxxxxxx
Build Information:
Version 0.99.5pre1 (SVN Rev 20499)
Copyright 1998-2007 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 with GTK+ 2.10.7, with GLib 2.12.7, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with Net-SNMP 5.4, with ADNS, with Lua 5.1,
with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio
PortAudio V19-devel, with AirPcap.
Running on Windows XP Service Pack 2, build 2600, with WinPcap version 3.1
(packet.dll version 3, 1, 0, 27), based on libpcap version 0.9[.x], without
AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Just downloaded 0.99.5pre1 and when I attempt to select an interface to capture
on, it displays the following error: "Can't get list of interfaces:
PacketGetAdapterNames: There are no more files. (18)". Then, no interfaces are
listed. I get the same results under the following circumstances:
- Click on the List Interfaces icon
- Choose Capture->"Interfaces..."
- Choose "Capture"->"Options..." or click Capture Options toolbar icon and
select Interface drop-down (error dialog is hidden and Capture Options
dialog is unresponsive until you find it and acknowledge the error)
- Run wireshark.exe with -D argument (same error in text window)
- Run tshark.exe with -D argument (error includes suggestion that issue may
be problem with WinPcap 3.0. I'm using WinPcap 3.1.)
I re-installed WinPcap3.1 with no effect. But, the issue did go away after I
loaded WinPcap4.0 beta3 ("... with WinPcap version 4.0 beta
3 (packet.dll version 4.0.0.703), based on libpcap version 0.9.5, without
AirPcap."). I hadn't noticed a new requirement for WinPcap 4.0 beta and I
thought the installer offered to install WinPcap3.1, still.
--
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.
