[Winpcap-bugs] PacketGetAdapterNames: The data area passed to asystem call is too small. (122)

[Greg Lee]

I figured something else interesting out today and want to report it.  If I
retry "windump -D" it will eventually succeed.  In one case I had to retry
several times before it would succeed.  Once it succeeds once it appears to
work each time after that (I repeated 10 times).  windump and WireShark
captures show the same symptom, if I repeat starting the capture it works
after several tries.
 
Greg

  _____  

From: Greg Lee [mailto:glee-list at swspec.com] 
Sent: Tuesday, September 25, 2007 2:02 PM
To: 'winpcap-bugs at winpcap.org'
Subject: RE: [Winpcap-bugs] PacketGetAdapterNames: The data area passed to
asystem call is too small. (122)


I forgot the attachment to the previous message.

  _____  

From: Greg Lee [mailto:glee-list at swspec.com] 
Sent: Tuesday, September 25, 2007 1:56 PM
To: winpcap-bugs at winpcap.org
Subject: RE: [Winpcap-bugs] PacketGetAdapterNames: The data area passed to
asystem call is too small. (122)


Certainly.  See attached files and report below.
 
1) First run windump -D with original packet.dll so that we verify the
problem still exists.
 
C:\Tools>windump -D
windump: PacketGetAdapterNames: The data area passed to a system call is too
small. (122)
 
2) Install debug packet.dll.
 
C:\Tools>ren packet.dll.2 packet.dll
 
3) Run windump -D with debug packet.dll.  Note that it works.
 
C:\Tools>windump -D
1.\Device\NPF_GenericDialupAdapter (Adapter for generic dialup and VPN
capture)
2.\Device\NPF_{4D1FBA71-F291-4653-8CEA-01D3FC82EFB6} ()
3.\Device\NPF_{7B4E25C5-963C-471E-8B6B-B188E034C227} (VMware Virtual
Ethernet Adapter)
4.\Device\NPF_{58E6FD8F-A6F8-457F-9F63-1989590EAEB3} (Dell Wireless 1470
Dual Band WLAN Mini-PCI Card (Microsoft's Packet Scheduler) )
5.\Device\NPF_{241D540D-9299-41FD-981F-DAD3E3552EF9} (VMware Virtual
Ethernet Adapter)
6.\Device\NPF_{71265B32-427A-438C-BEC1-434867A4156B} (Broadcom NetXtreme
Gigabit Ethernet Driver (Microsoft's Packet Scheduler) )

3) Verify the versions are as reported below.
 
C:\Tools>windump -V
windump version 3.9.5, based on tcpdump version 3.9.5
WinPcap version 4.0.1 (packet.dll version 4.0.0.901), based on libpcap
version 0.9.5
Usage: windump [-aAdDeflLnNOpqRStuUvxX] [ -B size ] [-c count] [ -C
file_size ]
                [ -E algo:secret ] [ -F file ] [ -i interface ] [ -M secret
]
                [ -r file ] [ -s snaplen ] [ -T type ] [ -w file ]
                [ -W filecount ] [ -y datalinktype ] [ -Z user ]
                [ expression ]
 
 
System description:
 
Windows XP SP2
Cisco Systems VPN Client version 4.8.01.0300
RSA Security Token software
 
 
Problem description:
 
I get the "PacketGetAdapterNames: The data area passed to a system call is
too small. (122)" message from WinDump and WireShark when I attempt to
capture packet the _second_ (and successive) time.
 
Greg


  _____  

From: Gianluca Varenni [mailto:gianluca.varenni at cacetech.com] 
Sent: Monday, September 24, 2007 8:29 PM
To: Greg Lee; winpcap-bugs at winpcap.org
Subject: Re: [Winpcap-bugs] PacketGetAdapterNames: The data area passed to
asystem call is too small. (122)


Can you please return the bug as described at
 
http://www.winpcap.org/bugs.htm
 
Have a nice day
GV


----- Original Message ----- 
From: Greg Lee <mailto:glee-list at swspec.com>  
To: winpcap-bugs at winpcap.org 
Sent: Monday, September 24, 2007 4:11 PM
Subject: [Winpcap-bugs] PacketGetAdapterNames: The data area passed to
asystem call is too small. (122)


I am getting the following message from both WinDump and WireShark.  This
appears to be a WinPcap problem.  I am running Windows XP SP2.  WireShark
was running fine about 2 weeks ago, now I'm seeing this error message the
_second_ (and successive) time I perform a capture.  The first time I run
the capture everything works fine.
 
C:\>windump -D
windump: PacketGetAdapterNames: The data area passed to a system call is too
small. (122)
 
C:\>windump -V
windump version 3.9.5, based on tcpdump version 3.9.5
WinPcap version 4.0.1 (packet.dll version 4.0.0.901), based on libpcap
version 0.9.5

Suggestions for how to diagnose this problem?
 
Greg
 




  _____  




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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winpcap.org/pipermail/winpcap-bugs/attachments/20070925/cce6ee6c/attachment.htm