Lines Matching +full:allow +full:- +full:set +full:- +full:time

22 pcap \- Packet Capture library
49 caller, as being in UTF-8.
51 On UNIX-like systems, the local character encoding is assumed to be
52 UTF-8, so no character encoding transformations are done.
62 does not attempt to handle UTF-16LE strings.
72 UTF-16LE string - note that this attempt is unsafe, as it may run past
73 the end of the string - to handle
75 returning a UTF-16LE string. Programs that don't call
115 to set up a handle for a ``savefile'', given a
141 The options that can be set on a capture handle include
144 requires more CPU time to copy the packet to your application, more disk
147 contents of the packet - for example, if you are only interested in the
148 TCP headers of packets - you can set the "snapshot length" for the
149 capture to an appropriate value.  If the snapshot length is set to
161 The snapshot length is set with
177 Note that even if an application does not set promiscuous mode, the
185 Promiscuous mode is set with
192 information pseudo-header for those frames.
196 receives, with 802.11 headers, and might supply a pseudo-header with
206 Monitor mode is set with
221 that a single wakeup would be done for multiple packets, and each set of
223 than a single packet.  This reduces the per-packet CPU overhead if
230 arbitrarily long period of time.
235 read to wait forever to allow enough packets to arrive, with no timeout.
241 packets to return within a limited period of time, because, on some
246 be used, for example, in an interactive application to allow the packet
251 The packet buffer timeout is set with
255 with no buffering.  Immediate mode is set with
260 some platforms, the buffer's size can be set; a size that's too small
265 non-pageable operating system memory than is necessary to prevent
268 The buffer size is set with
271 On some platforms, the time stamp given to packets on live captures can
273 can have different relationships to the time values for the current time
276 for a list of time stamp types.
278 The time stamp type is set with
294 allow
306 network pseudo-device - there is no need to change the privileges on
314 .B Under HP-UX with DLPI:
325 that supports capability bits such as CAP_NET_RAW and code to allow
327 those bits to be set on a user's initial processes when they log in, in
332 However, no user (not even the super-user) can capture in promiscuous
333 mode on an interface unless the super-user has enabled promiscuous-mode
336 and no user (not even the super-user) can capture unicast traffic
337 received by or sent by the machine on an interface unless the super-user
338 has enabled copy-all-mode operation on that interface using
343 promiscuous-mode or copy-all-mode operation, or both modes of
353 than just having somebody with super-user access setting the ownership
354 or permissions on the BPF devices - it might involve configuring devfs
355 to set the ownership or permissions every time the system is booted,
357 have to find some other way to make that happen at boot time.
361 The packets read from the handle may include a ``pseudo-header''
362 containing various forms of packet meta-data, and probably includes a
363 link-layer header whose contents can differ for different network
374 any given link-layer header type, such as
377 link-layer header type of
381 even if all devices on the system at the time the "any" device is opened
413 get first non-loopback device on that list
424 provide for packet time stamps
437 and specify the precision to provide for packet time stamps
448 set the snapshot length for a not-yet-activated
457 set promiscuous mode for a not-yet-activated
462 set capture protocol for a not-yet-activated
467 set monitor mode for a not-yet-activated
472 determine whether monitor mode can be set for a
477 set packet buffer timeout for a not-yet-activated
482 set immediate mode for a not-yet-activated
487 set buffer size for a not-yet-activated
492 set time stamp type for a not-yet-activated
497 get list of available time stamp types for a not-yet-activated
502 free list of available time stamp types
505 get name for a time stamp type
508 get description for a time stamp type
511 get time stamp type corresponding to a name
514 set time stamp precision for a not-yet-activated
519 get the time stamp precision of a
524 get link-layer header type for a
546 .SS Selecting a link-layer header type for a live capture
547 Some devices may provide more than one link-layer header type.  To
548 obtain a list of all link-layer header types provided by a device, call
553 To free a list of link-layer header types, call
555 To set the link-layer header type for a device, call
564 get a list of link-layer header types for a device
567 free list of link-layer header types
570 set link-layer header type for a device
573 get name for a link-layer header type
579 get description for a link-layer header type
583 get link-layer header type corresponding to a name
608 containing the time when the packet was captured
637 that is sufficiently large to get all of the packet's data - a value of
645 structure, and fills it in with the time stamp and length values for the
661 structure with the time stamp and length values for the packet, and sets
690 A handle can be put into ``non-blocking mode'', so that those routines
694 to put a handle into non-blocking mode or to take it out of non-blocking
697 to determine whether a handle is in non-blocking mode.  Note that
698 non-blocking mode does not work correctly in Mac OS X 10.6.
700 Non-blocking mode is often combined with routines such as
704 or other routines a platform offers to wait for any of a set of
715 .B \-1
750 open for a live capture or the full set of packets from a
776 set or clear non-blocking mode on a
780 get the state of non-blocking mode for a
801 packets, a filter can be set on a handle.  For a live capture, the
808 A filter string is compiled into a program in a pseudo-machine-language
831 compile filter expression to a pseudo-machine-language code program
877 to set up a handle for a ``savefile'', given a
932 will cause all buffered-but-not-yet-written packets to be written to the
1053 To report a security issue please send an e-mail to \%security@tcpdump.org.