WinPcap works on top of the network card drivers and does not have any control over the hardware itself.
>From what you say, you are running WinPcap in a QEMU virtual machine (which >I've never tested. I've extensively used WinPcap from within vmware). I don't >know what the "juniper patch" is. What other networking software do you have in this virtual machine? Do you have some VPN/firewall or similar software installed? Which version of Windows? Which version of WinPcap? Have a nice day GV -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Gianluca Varenni Sent: Wednesday, December 01, 2010 1:56 PM To: [email protected] Cc: [email protected] Subject: [Winpcap-users] winpcap nuked my interface ? [on behalf of Carlos G Mendioroz] [On behalf of Carlos G Mendioroz, for some unknown reason his messages don't get thru our mailing list server] I've run into a strange issue: soon after loading a program that uses pcap, the three interfaces I was trying to attach to reported "cable disconnected". I thought it was a parameters issue, but I've found that whatever went wrong, it has been made persistent at the hardware level! :( I.e. the interfaces htat I was trying to use do not get link up now even as the machine is doint POST. I've 1 atheros gigabit if, and 4 intel pro/100 ifs. The other 2 intel ports run fine. So question: what can possibly a program do using pcap that can force an interface to stay link down (i.e. no carrier) that is saved to the firmware ? If it matters, the client is qemu 0.11.0 with juniper patch, which adds pcap support. Any pointer is more than welcome! Thanks in advance, Carlos G Mendioroz _______________________________________________ Winpcap-users mailing list [email protected] https://www.winpcap.org/mailman/listinfo/winpcap-users _______________________________________________ Winpcap-users mailing list [email protected] https://www.winpcap.org/mailman/listinfo/winpcap-users
