https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5806
--- Comment #2 from Guy Harris <guy@xxxxxxxxxxxx> 2011-04-06 02:14:27 PDT ---
It looks as if WinPcap gets the adapter information from
HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}
in the Registry.
http://seclists.org/nmap-dev/2007/q4/419
says
"I'm not sure, but I found this comment in libdnet-stripped/src/intf-win32.c:
/* Next we must find the pcap device name corresponding to the device.
The device description used to be compared with those from
PacketGetAdapterNames(), but that was unrelaible because dnet and
pcap sometimes give different descriptions. For example, dnet gave
me "AMD PCNET Family PCI Ethernet Adapter - Packet Scheduler
Miniport" for one of my adapters (in vmware), while pcap described it
as "VMware Accelerated AMD PCNet Adapter (Microsoft's Packet
Scheduler)". Plus, Packet* functions aren't really supported for
external use by the WinPcap folks. So I have rewritten this to
compare interface addresses (which has its own problems -- what if
you want to listen an an interface with no IP address set?) --Fyodor */"
I don't know what calls dnet uses, but those might get different names.
Perhaps the names WinPcap are fetching are "type of interface" names, which
would be the same for all interfaces of a given type, and dnet and the Windows
tool you're using fetch per-interface names.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
