PCAP_OPEN_LIVE(3PCAP)PCAP_OPEN_LIVE(3PCAP)NAME
pcap_open_live - open a device for capturing
SYNOPSIS
#include <pcap/pcap.h>
char errbuf[PCAP_ERRBUF_SIZE];
pcap_t *pcap_open_live(const char *device, int snaplen,
int promisc, int to_ms, char *errbuf);
DESCRIPTION
pcap_open_live() is used to obtain a packet capture handle to look at packets on the network. device is a string that specifies the net-
work device to open; on Linux systems with 2.2 or later kernels, a device argument of "any" or NULL can be used to capture packets from all
interfaces.
snaplen specifies the snapshot length to be set on the handle.
promisc specifies if the interface is to be put into promiscuous mode.
to_ms specifies the read timeout in milliseconds.
RETURN VALUE
pcap_open_live() returns a pcap_t * on success and NULL on failure. If NULL is returned, errbuf is filled in with an appropriate error
message. errbuf may also be set to warning text when pcap_open_live() succeeds; to detect this case the caller should store a zero-length
string in errbuf before calling pcap_open_live() and display the warning to the user if errbuf is no longer a zero-length string. errbuf
is assumed to be able to hold at least PCAP_ERRBUF_SIZE chars.
SEE ALSO pcap(3PCAP), pcap_create(3PCAP), pcap_activate(3PCAP)
5 April 2008 PCAP_OPEN_LIVE(3PCAP)
Check Out this Related Man Page
PCAP_OPEN_LIVE(3PCAP)PCAP_OPEN_LIVE(3PCAP)NAME
pcap_open_live - open a device for capturing
SYNOPSIS
#include <pcap/pcap.h>
char errbuf[PCAP_ERRBUF_SIZE];
pcap_t *pcap_open_live(const char *device, int snaplen,
int promisc, int to_ms, char *errbuf);
DESCRIPTION
pcap_open_live() is used to obtain a packet capture handle to look at packets on the network. device is a string that specifies the net-
work device to open; on Linux systems with 2.2 or later kernels, a device argument of "any" or NULL can be used to capture packets from all
interfaces.
snaplen specifies the snapshot length to be set on the handle.
promisc specifies if the interface is to be put into promiscuous mode.
to_ms specifies the read timeout in milliseconds.
RETURN VALUE
pcap_open_live() returns a pcap_t * on success and NULL on failure. If NULL is returned, errbuf is filled in with an appropriate error
message. errbuf may also be set to warning text when pcap_open_live() succeeds; to detect this case the caller should store a zero-length
string in errbuf before calling pcap_open_live() and display the warning to the user if errbuf is no longer a zero-length string. errbuf
is assumed to be able to hold at least PCAP_ERRBUF_SIZE chars.
SEE ALSO pcap(3PCAP), pcap_create(3PCAP), pcap_activate(3PCAP)
5 April 2008 PCAP_OPEN_LIVE(3PCAP)
hi
plz help me modifying the following code (use pcap) to include concepts of parallel programming or multi threading. I am trying from the past 1 week to change the code and apply concepts of threads but have been unsuccessful.. pls guide me..
/* This section contains additional information... (1 Reply)
HI
For the past 1 week i have been trying to include the concepts of parallel programming or thread in the sniffex.c code. Haven't been able to..
Please suggest sm appropriate modifications to the following code:
/*
* sniffex.c
*
* Sniffer example of TCP/IP packet capture using... (1 Reply)
I want to write a small application using Libpcap in C on Linux.
Currently, it starts to sniff and waits for the packets. But that's not what I need actually. I want it to wait for N seconds and then stop listening. (I think there's something wrong with my usage of 'pcap_open_live'...)
How... (0 Replies)
Hi all
My application is a monitoring application that monitors the incoming udp packet when ever required. When ever a particular source ip and port and dest ip and port is provided the filter will be framed based them. For eg,
char filterExpr;
filterExpr = "udp and src host 192.168.16.100... (0 Replies)
Hi Guys,
What do I need to do to set an physical adapter to promiscuous mode?
The networkport is already spanned/mirrored.
Is this also possible when there is an virtual nic (through vios) configured?
regards,
Randy (7 Replies)