SECURITY WARNING: You are receiving a message with an attachment that may be harmful once extracted. Please do not click on any files unless you are expecting this message and a trusted sender verified that the file originated from them. If in doubt, please
forward the message to security@xxxxxxx for inspection. =========================================
Hello Yang,
I did not use a VM to test Npcap 0.04. The two Windows 8.1 systems I tested with were running Windows directly on the hardware.
I installed the 0.04-r2-debug-2 image but (as expected) the Npcap Loopback adapter was not visible to Wireshark. I started DebugView, I enabled the two additional DebugView options you requested, I installed Npcap 0.04-r3-debug-2, I waited for perhaps 15
to 20 seconds and then started Wireshark. I left Wireshark up for several seconds then shut it down because there was no loopback adapter. I let DebugTest run for a few minutes before grabbing the attached log file.
I hope you find something useful in the log.
Jim Y.
From: wireshark-dev-bounces@xxxxxxxxxxxxx <wireshark-dev-bounces@xxxxxxxxxxxxx> on behalf of Yang Luo <hsluoyb@xxxxxxxxx>
Sent: Sunday, August 16, 2015 23:12
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Npcap 0.04 call for test
Hi Jim,
Did you also use a VirtualBox guest to test Npcap 0.04? I think the cause is the same with Pascal: I added Winsock Kernel init code to loopback interface's OpenAdapter op, if the init fails, the adapter fails to be opened. There're also two ways, first
provide me the reproduce steps if you think it's viable. The second is to use the debug version, I have updated the version to 0.04-r2, you can use the debug one and give me the DebugView text I documented for Pascal.
Improvements in Npcap 0.04-r2:
1) Wireshark now can see Npcap version 0.04 instead of 0.03.
2) Added some trace message for WSK.
Lastest installer:
Lastest debug installer:
Cheers,
Yang
|
Attachment:
JYNUC01.02.LOG.zip
Description: JYNUC01.02.LOG.zip
