[Winpcap-users] WinPcap 3.1 equivalent
ofPCAP_OPENFLAG_NOCAPTURE_LOCAL flag
Gianluca Varenni
gianluca.varenni at cacetech.com
Fri May 26 14:47:10 GMT 2006
----- Original Message -----
From: "Marcel van Lieshout" <marcel at hmcs.nl>
To: <winpcap-users at winpcap.org>
Sent: Friday, May 26, 2006 1:43 AM
Subject: Re: [Winpcap-users] WinPcap 3.1 equivalent
ofPCAP_OPENFLAG_NOCAPTURE_LOCAL flag
> Ok, moved to 4.0A. I hope it's stability is ok.
We were pretty happy about its stability in our internal tests, but we
decided to go out with an alpha for this precise reason: having more and
more people testing it (hopefully), and reporting any strange behavior.
Have a nice day
GV
>
> Thanks!
>
> Marcel
>
> Loris Degioanni wrote:
>> PCAP_OPENFLAG_NOCAPTURE_LOCAL (and the related functionality in the
>> driver) has been introduced after 3.1, therefore if you need it you
>> are forced to use 4.0a.
>>
>> Loris
>>
>>
>> Marcel van Lieshout wrote:
>>> How can I prevent the capture of packets sent by myself with
>>> pcap_sendpacket()?
>>>
>>> An alternative would be to move to WinPcap 4.0. But I'm not sure
>>> about stability.
>>>
>>> Marcel
>>> _______________________________________________
>>> Winpcap-users mailing list
>>> Winpcap-users at winpcap.org
>>> https://www.winpcap.org/mailman/listinfo/winpcap-users
>>>
>> _______________________________________________
>> Winpcap-users mailing list
>> Winpcap-users at winpcap.org
>> https://www.winpcap.org/mailman/listinfo/winpcap-users
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users
More information about the Winpcap-users
mailing list