From: Aldobino Braga [mailto:ambraga@xxxxxxxxxxx]
Sent: 03 September 2002 15:04
> how does Ethereal get what it calls the device interface in windows?
An interesting question.
The short answer is "from WinPcap."
The longer answer is that it is strongly related to the registry keys
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\NetworkCards\1\ServiceName
and
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\NetworkCards\1\Descripton
(I would imagine that a second NIC would use keys "...\2\...")
For Example, my registry reads:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\NetworkCards\1]
"ServiceName"="{95962D06-A226-42F2-A6BB-373D708BC50B}"
"Description"="3Com EtherLink 10/100 PCI TX NIC (3C905B-TX)"
and Etheral first offers interface
3Com EtherLink PCI: \Device\Packet_{95962D06-A226-42F2-A6BB-373D708BC50B}
and subsiquently
\Device\Packet_{95962D06-A226-42F2-A6BB-373D708BC50B}
So that isn't the whole story; something has created a description "3COM
EtherLink PCI", and it probably isn't done by reference to the registry. But
if the number (GUID) is all you are after, this probably doesn't matter.
--
Richard Urwin, Private
"No 9000 series computer has ever made a mitsake or corrubiteddatatato."
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
