1 .\" Copyright (c) 1994, 1996, 1997
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that: (1) source code distributions
6 .\" retain the above copyright notice and this paragraph in its entirety, (2)
7 .\" distributions including binary code include the above copyright notice and
8 .\" this paragraph in its entirety in the documentation or other materials
9 .\" provided with the distribution, and (3) all advertising materials mentioning
10 .\" features or use of this software display the following acknowledgement:
11 .\" ``This product includes software developed by the University of California,
12 .\" Lawrence Berkeley Laboratory and its contributors.'' Neither the name of
13 .\" the University nor the names of its contributors may be used to endorse
14 .\" or promote products derived from this software without specific prior
15 .\" written permission.
16 .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
17 .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
18 .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
20 .TH PCAP_LOOP 3PCAP "5 March 2022"
22 pcap_loop, pcap_dispatch \- process packets from a live capture or savefile
26 #include <pcap/pcap.h>
30 typedef void (*pcap_handler)(u_char *user, const struct pcap_pkthdr *h,
32 int pcap_loop(pcap_t *p, int cnt,
33 pcap_handler callback, u_char *user);
34 int pcap_dispatch(pcap_t *p, int cnt,
35 pcap_handler callback, u_char *user);
40 processes packets from a live capture or ``savefile'' until
42 packets are processed, the end of the ``savefile'' is
43 reached when reading from a ``savefile'',
44 .BR pcap_breakloop (3PCAP)
45 is called, or an error occurs.
48 return when live packet buffer timeouts occur.
55 is equivalent to infinity, so that packets are processed until another
56 ending condition occurs.
59 processes packets from a live capture or ``savefile'' until
61 packets are processed, the end of the current bufferful of packets is
62 reached when doing a live capture, the end of the ``savefile'' is
63 reached when reading from a ``savefile'',
65 is called, or an error occurs.
66 Thus, when doing a live capture,
68 is the maximum number of packets to process before returning, but is not
69 a minimum number; when reading a live capture, only one
70 bufferful of packets is read at a time, so fewer than
72 packets may be processed. A value of
78 causes all the packets received in one buffer to be processed when
79 reading a live capture, and causes all the packets in the file to be
80 processed when reading a ``savefile''.
82 Note that, when doing a live capture on some platforms, if the read
83 timeout expires when there are no packets available,
85 will return 0, even when not in non-blocking mode, as there are no
86 packets to process. Applications should be prepared for this to happen,
87 but must not rely on it happening.
92 routine to be called with three arguments:
95 pointer which is passed in the
100 .BR pcap_dispatch (),
102 .B const struct pcap_pkthdr
103 pointer pointing to the packet time stamp and lengths, and a
108 .BR "struct pcap_pkthdr" ,
109 a pointer to which is passed to the callback routine)
110 bytes of data from the packet. The
111 .B struct pcap_pkthdr
112 and the packet data are not to be freed by the callback routine, and are
113 not guaranteed to be valid after the callback routine returns; if the
114 code needs them to be valid after the callback, it must make a copy of
117 The bytes of data from the packet begin with a link-layer header. The
118 format of the link-layer header is indicated by the return value of the
119 .BR pcap_datalink (3PCAP)
120 routine when handed the
125 .BR pcap_dispatch ().
126 .I https://www.tcpdump.org/linktypes.html
129 can return and describes the packet formats that
130 correspond to those values. The value it returns will be valid for all
131 packets received unless and until
132 .BR pcap_set_datalink (3PCAP)
133 is called; after a successful call to
134 .BR pcap_set_datalink (),
135 all subsequent packets will have a link-layer header of the type
136 specified by the link-layer header type value passed to
137 .BR pcap_set_datalink ().
141 assume that the packets for a given capture or ``savefile`` will have
142 any given link-layer header type, such as
144 for Ethernet. For example, the "any" device on Linux will have a
145 link-layer header type of
149 even if all devices on the system at the time the "any" device is opened
150 have some other data link type, such as
159 is exhausted or if, when reading from a ``savefile'', no more packets
160 are available. It returns
162 if the loop terminated due to a call to
163 .BR pcap_breakloop ()
164 before any packets were processed,
165 .B PCAP_ERROR_NOT_ACTIVATED
166 if called on a capture handle that has been created but not activated,
169 if another error occurs.
172 return when live packet buffer timeouts occur; instead, it attempts to
176 returns the number of packets processed on success; this can be 0 if no
177 packets were read from a live capture (if, for example, they were
178 discarded because they didn't pass the packet filter, or if, on
179 platforms that support a packet buffer timeout that starts before any
180 packets arrive, the timeout expires before any packets arrive, or if the
181 file descriptor for the capture device is in non-blocking mode and no
182 packets were available to be read) or if no more packets are available
183 in a ``savefile''. It returns
185 if the loop terminated due to a call to
186 .BR pcap_breakloop ()
187 before any packets were processed,
188 .B PCAP_ERROR_NOT_ACTIVATED
189 if called on a capture handle that has been created but not activated,
192 if another error occurs.
194 If your application uses pcap_breakloop(),
195 make sure that you explicitly check for PCAP_ERROR and PCAP_ERROR_BREAK,
196 rather than just checking for a return value < 0.
202 .BR pcap_geterr (3PCAP)
204 .BR pcap_perror (3PCAP)
207 as an argument to fetch or display the error text.
208 .SH BACKWARD COMPATIBILITY
210 In libpcap versions before 1.5.0, the behavior when
214 was undefined; different platforms and devices behaved differently,
215 so code that must work with these versions of libpcap should use