Wireshark-dev: Re: [Wireshark-dev] Npcap 0.01 call for test (2nd)
From: Tyson Key <[email protected]>
Date: Sun, 19 Jul 2015 16:16:52 +0100
PS - No joy with manually running "NPFInstall.exe -ul" multiple times, to remove the redundant interfaces, so I had to resort to uninstalling them using Device Manager, and then rebooting.

2015-07-19 15:37 GMT+01:00 Tyson Key <[email protected]>:
Hi Yang,

Just downloaded your latest package, and here's my experience, so far:

After uninstalling the old WinPCap 4.1.3, and installing your new package (without rebooting), I get as far as "NPFInstall.exe - il" (which stalls for a while, but then continues, on my machine), and then continue to "NPFInstall.exe -iw". 

At this stage, it appears that some driver files from the old version are still present, and Windows Explorer asks me if I want to replace them with "older" (i.e. the latest?) versions, for some reason (maybe the uninstaller isn't cleaning things up properly, on x86-64 machines?); before the correctly-named "Npcap Loopback Adaptor" gets installed (and then does a quick vanishing act (guessing that it tried to rename one of the myriad KM-TEST interfaces from earlier), before reappearing). Afterwards, I receive "The npf service for Win7 and Win8 was successfully created" - but starting Wireshark results in "The NPF driver isn't running.  You may have trouble
capturing or listing interfaces".

I'll follow up with my results of rebooting, shortly - but in the meantime, it might be a good idea to have the installer (and uninstaller) be smarter about removing older copies of the drivers, and try to automatically purge old instances of the loopback adaptor, if they exist.

I hope that helps,

Tyson.  

2015-07-18 13:13 GMT+01:00 Yang Luo <[email protected]>:
Hi list,

Thanks for your tests for the first version Npcap, in this 2nd version, I have fixed several problems as following:
1) Npcap driver fails to start after system reboot.
2) Adapter name is not changed to "Npcap Loopback Adapter" on Win10.
3) BSoD caused by BAD_POOL_CALLER. I can't promise this BSoD is 100% fixed, but I have secured pool memory free function calls which may lead to BSoD. If this still occurs, please let me know.
4) Npcap now will try to capture WAN adapter packets, I only switched on this feature and it does not get tested, as I don't have a WAN adapter on hand. If this feature has caused problems, or you know how to simulate a WAN adapter for me to test, please tell me.


I have tested this version Npcap under Wireshark 1.12.6 x64, in Windows 7 x86, Windows 8.1 x64 and Windows Server 2016 TP2.

Notice: You need to try it under Win7 and later, and no need to change the installation options, just click the "Next"s. Npcap installed in "WinPcap Compatible Mode" is exclusive with WinPcap, so you must uninstall WinPcap first (installer will prompt you this).

The README is:


Cheers,
Yang

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe



--
                                          Fight Internet Censorship! http://www.eff.org
http://vmlemon.wordpress.com | Twitter/FriendFeed/Skype: vmlemon | 00447934365844



--
                                          Fight Internet Censorship! http://www.eff.org
http://vmlemon.wordpress.com | Twitter/FriendFeed/Skype: vmlemon | 00447934365844