Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 6088] New: Interface names not usefull

Date: Sun, 3 Jul 2011 15:21:12 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6088

           Summary: Interface names not usefull
           Product: Wireshark
           Version: 1.6.0
          Platform: x86-64
        OS/Version: Windows 7
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: bernd-2011@xxxxxxxxxxxxx


Created an attachment (id=6609)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6609)
screenshot interface list and details

Build Information:
Version 1.6.0 (SVN Rev 37592 from /trunk-1.6)

Compiled (64-bit) with GTK+ 2.22.1, with GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, without
SMI, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3, with
Gcrypt 1.4.6, without Kerberos, with GeoIP, with PortAudio V19-devel (built Jun 
7 2011), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 21022

(official download)
--
On my system the Wireshark Interface list gives non-helpfull Interface names
("Microsoft") for WLAN and Bluetooth. However other tools see much more
helpfull names:

netstat-r:
 13...00 27 10 7a xx xx ......Intel(R) Centrino(R) Advanced-N 6200 AGN
 12...00 26 0a 06 xx xx ......Intel(R) 82577LM Gigabit Network Connection
 10...5c ac 4c fc xx xx ......Bluetooth-Gerät (PAN)
  1...........................Software Loopback Interface 1

netsh int ipv4 show interface
Idx     Met         MTU          State                Name
---  ----------  ----------  ------------  ---------------------------
  1          50  4294967295  connected     Loopback Pseudo-Interface 1
 13          25        1500  connected     WLAN
 10          40        1500  disconnected  Bluetooth-Netzwerkverbindung
 12           5        1500  disconnected  LAN-Verbindung

The problem might be related to the fact, that it is using Microsoft device
drivers, however 3 out of 4 driver DLLs seem to be from Intel.

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