Hi Guy,
On Mon, Aug 17, 2015 at 11:02 AM, Guy Harris wrote:
>
> On Aug 16, 2015, at 7:39 PM, Jim Young wrote:
>
> > But unlike the earlier versions, the NPcap Loopback Adapter does no
> longer shows up in the list of interfaces available to Wireshark.
>
> I suspect the most likely reason for th
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
On Aug 16, 2015, at 7:39 PM, Jim Young wrote:
> But unlike the earlier versions, the NPcap Loopback Adapter does no longer
> shows up in the list of interfaces available to Wireshark.
I suspect the most likely reason for this would either be that
1) PacketGetAdapterNames() doesn't lis
Hello Yang,
I have attempted to test Npcap 0.04 on my primary Windows 8.1 machine.
After uninstalling any previous WinPCap or Npcap I rebooted and then
successfully installed Npcap 0.04.
The Npcap Loopback Adapter shows up in the list from the Device Manager's
Network adapter.
The good ne
Hi Pascal,
Thanks for test. It's my typo mistake for the BSoD word, what I meant is
the loopback interface didn't show problem, in fact they share the same
cause. Because I didn't handle the error correctly in 0.03 r5 and r6, so it
turns to a BSoD.
On Sun, Aug 16, 2015 at 11:55 PM, Pascal Quanti
Le 16 août 2015 3:39 PM, "Pascal Quantin" a
écrit :
>
> Hi Yang,
>
> 2015-08-16 14:18 GMT+02:00 Yang Luo :
>>
>> Hi Pascal,
>>
>> I think this BSoD is caused by the Winsock Kernel init code in Npcap
driver (NPF_WSKStartup call or NPF_WSKInitSockets call failed). I can't
reproduce it on my Win8.1 V
Hi Pascal,
I think this BSoD is caused by the Winsock Kernel init code in Npcap driver
(*NPF_WSKStartup* call or *NPF_WSKInitSockets* call failed). I can't
reproduce it on my Win8.1 VM, Win10 VM and Win10 physical host. I used
VMware Workstation 11.1.2 for my VMs. I don't know which type your VM i
