|
Macros | |
| #define | PCAP_OPENFLAG_DATATX_UDP 2 |
| Defines if the data trasfer (in case of a remote capture) has to be done with UDP protocol. More... | |
| #define | PCAP_OPENFLAG_MAX_RESPONSIVENESS 16 |
| This flag configures the adapter for maximum responsiveness. More... | |
| #define | PCAP_OPENFLAG_NOCAPTURE_LOCAL 8 |
| Defines if the local adapter will capture its own generated traffic. More... | |
| #define | PCAP_OPENFLAG_NOCAPTURE_RPCAP 4 |
| Defines if the remote probe will capture its own generated traffic. More... | |
| #define | PCAP_OPENFLAG_PROMISCUOUS 1 |
| Defines if the adapter has to go in promiscuous mode. More... | |
Detailed Description
Macro Definition Documentation
◆ PCAP_OPENFLAG_DATATX_UDP
| #define PCAP_OPENFLAG_DATATX_UDP 2 |
Defines if the data trasfer (in case of a remote capture) has to be done with UDP protocol.
If it is '1' if you want a UDP data connection, '0' if you want a TCP data connection; control connection is always TCP-based. A UDP connection is much lighter, but it does not guarantee that all the captured packets arrive to the client workstation. Moreover, it could be harmful in case of network congestion. This flag is meaningless if the source is not a remote interface. In that case, it is simply ignored.
Definition at line 217 of file remote-ext.h.
◆ PCAP_OPENFLAG_MAX_RESPONSIVENESS
| #define PCAP_OPENFLAG_MAX_RESPONSIVENESS 16 |
This flag configures the adapter for maximum responsiveness.
In presence of a large value for nbytes, WinPcap waits for the arrival of several packets before copying the data to the user. This guarantees a low number of system calls, i.e. lower processor usage, i.e. better performance, which is good for applications like sniffers. If the user sets the PCAP_OPENFLAG_MAX_RESPONSIVENESS flag, the capture driver will copy the packets as soon as the application is ready to receive them. This is suggested for real time applications (like, for example, a bridge) that need the best responsiveness.
Definition at line 248 of file remote-ext.h.
◆ PCAP_OPENFLAG_NOCAPTURE_LOCAL
| #define PCAP_OPENFLAG_NOCAPTURE_LOCAL 8 |
Defines if the local adapter will capture its own generated traffic.
This flag tells the underlying capture driver to drop the packets that were sent by itself. This is usefult when building applications like bridges, that should ignore the traffic they just sent.
Definition at line 237 of file remote-ext.h.
◆ PCAP_OPENFLAG_NOCAPTURE_RPCAP
| #define PCAP_OPENFLAG_NOCAPTURE_RPCAP 4 |
Defines if the remote probe will capture its own generated traffic.
In case the remote probe uses the same interface to capture traffic and to send data back to the caller, the captured traffic includes the RPCAP traffic as well. If this flag is turned on, the RPCAP traffic is excluded from the capture, so that the trace returned back to the collector is does not include this traffic.
Definition at line 228 of file remote-ext.h.
◆ PCAP_OPENFLAG_PROMISCUOUS
| #define PCAP_OPENFLAG_PROMISCUOUS 1 |
Defines if the adapter has to go in promiscuous mode.
It is '1' if you have to open the adapter in promiscuous mode, '0' otherwise. Note that even if this parameter is false, the interface could well be in promiscuous mode for some other reason (for example because another capture process with promiscuous mode enabled is currently using that interface). On on Linux systems with 2.2 or later kernels (that have the "any" device), this flag does not work on the "any" device; if an argument of "any" is supplied, the 'promisc' flag is ignored.
Definition at line 203 of file remote-ext.h.