Lines Matching +full:machine +full:- +full:mode
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
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
163 .IP "promiscuous mode"
172 adapters support "promiscuous mode", which is a mode in which all
177 Note that even if an application does not set promiscuous mode, the
178 adapter could well be in promiscuous mode for some other reason.
183 is supplied, the setting of promiscuous mode is ignored.
185 Promiscuous mode is set with
187 .IP "monitor mode"
188 On IEEE 802.11 wireless LANs, even if an adapter is in promiscuous mode,
192 information pseudo-header for those frames.
194 In "monitor mode", sometimes also called "rfmon mode" (for "Radio
196 receives, with 802.11 headers, and might supply a pseudo-header with
199 Note that in monitor mode the adapter might disassociate from the
203 if you are capturing in monitor mode and are not connected to another
206 Monitor mode is set with
211 mode.
223 than a single packet. This reduces the per-packet CPU overhead if
253 .IP "immediate mode"
254 In immediate mode, packets are always delivered as soon as they arrive,
255 with no buffering. Immediate mode is set with
265 non-pageable operating system memory than is necessary to prevent
296 to capture in promiscuous mode; on those versions of Solaris, you must
299 mode. Note that, on many (perhaps all) interfaces, if you don't capture
300 in promiscuous mode, you will not see any outgoing packets, so a capture
301 not done in promiscuous mode may not be very useful.
306 network pseudo-device - there is no need to change the privileges on
314 .B Under HP-UX with DLPI:
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
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
413 get first non-loopback device on that list
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
514 set time stamp precision for a not-yet-activated
524 get link-layer header type for a
535 determine whether a ``savefile'' being read came from a machine with the
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
637 that is sufficiently large to get all of the packet's data - a value of
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
695 mode; call
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
715 .B \-1
776 set or clear non-blocking mode on a
780 get the state of non-blocking mode for a
802 filtering will be performed in kernel mode, if possible, to avoid
803 copying ``uninteresting'' packets from the kernel to user mode.
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
848 machine and packets received by the machine. To limit it to capturing
849 only packets received by the machine or, if possible, only packets sent
850 by the machine, call
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.