[Winpcap-users] winpcap nuked my interface ? [on behalf of Carlos G Mendioroz]
Gianluca.Varenni at riverbed.com
Wed Dec 1 13:55:45 PST 2010
[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
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
More information about the Winpcap-users