Pressing the Refresh Interfaces button did not fix it. I fired up Wireshark and got the message "No interface can be used for capturing in this system with the current configuration.". Everything installed fine and WinPcap installed normally.
On March 23 I upgraded 9926 to 10041 and then installed Wireshark 圆4 v1.12.4 from. Physical network adapter in the Shuttle is Generic Marvell Yukon 88E8056 based Ethernet controller. Network Adapter in the VM is in Bridged mode. Even the last version 9926 worked OK, but now we have a problem - a big problem.Ībout the test machine: Shuttle xpc, quad core cpu, 8GB RAM. Host OS is Windows 7 圆4. Windows 10 圆4 Enterprise 10041 is a guest OS running inside VirtualBox 4.3.26 r98988. Up until release 10041 all Windows 10 Tech Preview versions have appeared to run WinPcap 4.1.3 without a problem. Update 3-26-15: This has been confirmed by others and a thread has been started here: Update 3-27-15: Do you want to use Wireshark on Windows 10? Tweet about this problem! do a post about this issue. Another issue is driver signing: in Windows 10 圆4 that really will be changing, so it will be important for WinPcap to be updated before the RTM release - more about this here.
Work has been done on this at NMAP and has been shared, so it would be great if could expand on that work and release WinPcap fully compatible with NDIS6. But we still need to encourage Riverbed to update WinPcap from NDIS5 to NDIS6. Hopefully, this trend continues - but I wouldn't count on it. Update May 13, 2015: WinPcap 4.1.3 began to work again in Windows 10 preview 10061 and continues to operate in 10074.
0 kommentar(er)
