Searched refs:libpcap (Results 1 – 5 of 5) sorted by relevance
49 The biggest user of this construct might be libpcap. Issuing a high-level50 filter command like `tcpdump -i em1 port 22` passes through the libpcap168 covered by libpcap in high-level syntax, so as an application developer169 you should stick to that. libpcap wraps its own layer around all that.171 Unless i) using/linking to libpcap is not an option, ii) the required BPF172 filters use Linux extensions that are not supported by libpcap's compiler,174 libpcap's compiler, or iv) particular filter codes should be optimized175 differently than libpcap's internal compiler does; then in such cases178 more complex filter code, or one that cannot be expressed with libpcap
31 (like libpcap always does).53 From the user standpoint, you should use the higher level libpcap library, which57 Packet MMAP support was integrated into libpcap around the time of version 1.3.0;
441 …--disable-shared --without-ndiff --without-zenmap --without-nping --with-libpcap=included --with-l…442 $(MAKE) -C $(NMAP_PATH)/libpcap
52 PCAP_CFLAGS := $(shell $(PKG_CONFIG) --cflags libpcap 2>/dev/null && echo "-DTRAFFIC_MONITOR=1")53 PCAP_LIBS := $(shell $(PKG_CONFIG) --libs libpcap 2>/dev/null)
113 ``libpcap``. The tagging protocol driver must populate the ``proto`` member of