[Winpcap-users] Adapter description bug

[Gianluca Varenni]

Can you please report the problem using the tracing version of packet.dll 
available at

http://www.winpcap.org/bugs.htm

I will need the winpcap_debug.txt file.

Have a nice day
GV


----- Original Message ----- 
From: "Gisle Vanem" <gvanem at broadpark.no>
To: "WinDump" <winpcap-users at winpcap.org>
Sent: Wednesday, February 18, 2009 3:04 AM
Subject: [Winpcap-users] Adapter description bug


> I'm having troubles getting at the adapter-descriptions from
> pcap_findalldevs(). I've modified  fad-win32.c from libpcap-Git
> to dump the 'AdaptersName' buffer. See the attachment.
>
> Here is now what findalldevtest.exe prints:
>
> G:\MingW32\src\inet\libpcap>findalldevstest.exe
> 336:   0000: 5C 5C 2E 5C 61 69 72 70-63 61 70 30 30 00 5C 44 
> \\.\airpcap00.\D
>       0010: 65 76 69 63 65 5C 4E 50-46 5F 7B 45 32 33 31 30 
> evice\NPF_{E2310
>       0020: 32 46 36 2D 32 44 37 36-2D 34 45 46 37 2D 38 39 
> 2F6-2D76-4EF7-89
>       0030: 42 45 2D 38 43 30 37 35-44 38 36 39 44 43 42 7D 
> BE-8C075D869DCB}
>       0040: 00 5C 44 65 76 69 63 65-5C 4E 50 46 5F 7B 37 46 
> .\Device\NPF_{7F
>       0050: 35 36 33 35 32 45 2D 45-46 32 46 2D 34 39 46 34 
> 56352E-EF2F-49F4
>       0060: 2D 38 34 34 43 2D 42 41-31 46 41 30 31 30 35 
> 36 -844C-BA1FA01056
>       0070: 36 37 7D 00 5C 44 65 76-69 63 65 5C 4E 50 46 5F 
> 67}.\Device\NPF_
>       0080: 7B 39 33 33 38 30 36 39-35 2D 30 45 33 31 2D 34 
> {93380695-0E31-4
>       0090: 35 36 43 2D 39 45 42 30-2D 38 38 30 32 45 31 31 
> 56C-9EB0-8802E11
>       00A0: 31 43 30 39 44 7D 00 00-00 00 00 00 00 00 00 00 
> 1C09D}..........
>       00B0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 
> ................
>       00C0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 
> ................
>       00D0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 
> ................
>       00E0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 
> ................
>       00F0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 
> ................
>       0100: 00 00 52 65 61 6C 74 65-6B 20 52 54 4C 38 31 33 ..Realtek 
> RTL813
>       0110: 39 20 46 61 6D 69 6C 79-20 46 61 73 74 20 45 74 9 Family Fast 
> Et
>       0120: 68 65 72 6E 65 74 20 41-64 61 70 74 65 72 20 28 hernet Adapter 
> (
>       0130: 4D 69 63 72 6F 73 6F 66-74 27 73 20 50 61 63 6B Microsoft's 
> Pack
>       0140: 65 74 20 53 63 68 65 64-75 6C 65 72 29 20 00 00 et Scheduler) 
> ..
> \\.\airpcap00
>        Description:
>        Loopback: no
>
> \Device\NPF_{7F56352E-EF2F-49F4-844C-BA1FA0105667}
>        Description:
>        Loopback: no
>
> \Device\NPF_{E23102F6-2D76-4EF7-89BE-8C075D869DCB}
>        Description:
>        Loopback: no
>        Address Family: AF_INET
>                Address: 192.168.0.1
>                Netmask: 255.255.255.0
>                Broadcast Address: 255.255.255.255
>
> \Device\NPF_{93380695-0E31-456C-9EB0-8802E111C09D}
>        Description:
>        Loopback: no
>        Address Family: AF_INET
>                Address: 10.0.0.6
>                Netmask: 255.255.255.0
>                Broadcast Address: 255.255.255.255
>
> Preferred device name: \\.\airpcap00
> Preferred device is on network: 0.0.0.0/0.0.0.0
>
> -------------
>
> Notice all the NULLs after the adapter-names? There should be only 2,
> should there? And the buffer seems truncated; only the description from
> my Realtek (10.0.06) adapter is there
> (\Device\NPF_{93380695-0E31-456C-9EB0-8802E111C09D}).
>
> I'm using the latest libpcap from Git with WinPcap 4.1beta5 (npf 
> 4.1.0.1452).
>
> --gv
>


--------------------------------------------------------------------------------


> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users
>