Lines Matching full:packet
42 implementation in the libpcap/WinPcap packet capture library.
72 3.3 Packet Block (optional) . . . . . . . . . . . . . . . . . . . 13
73 3.4 Simple Packet Block (optional) . . . . . . . . . . . . . . . . 15
78 5.1 Other Packet Blocks (experimental) . . . . . . . . . . . . . . 23
120 The problem of exchanging packet traces becomes more and more
122 this task right now. One of the most accepted packet interchange
127 This document proposes a new format for dumping packet traces. The
242 3. Packet Block: it contains a single captured packet, or a portion
245 4. Simple Packet Block: it contains a single captured packet, or a
249 addresses present in the packet dump and the canonical name
253 statistical data (e.g. packet dropped, etc) which can be useful
266 1. Further Packet Blocks
536 sections of the file. The Interface ID is referenced by the packet
542 o SnapLen: maximum number of bytes dumped from each packet. The
543 portion of each packet that exceeds this value will not be stored
713 3.3 Packet Block (optional)
715 A Packet Block is the standard container for storing the packets
716 coming from the network. The Packet Block is optional because packets
717 can be stored either by means of this block or the Simple Packet
719 packet block is shown in Figure 5.
756 | Packet Len |
759 | Packet Data |
769 Figure 5: Packet Block format.
771 The Packet Block has the following fields:
773 o Interface ID: Specifies the interface this packet comes from, and
779 this packet and the preceding one. The value xFFFF (in
789 this packet. If the Interface Description block does not contain a
792 o Captured Len: number of bytes captured from the packet (i.e. the
802 length of the Packet Data field). It will be the minimum value
803 among the actual Packet Length and the snapshot length (defined in
806 o Packet Len: actual length of the packet when it was transmitted on
808 packet.
810 o Packet Data: the data coming from the network, including
820 3.4 Simple Packet Block (optional)
822 The Simple Packet Block is a lightweight container for storing the
825 A Simple Packet Block is similar to a Packet Block (see Section 3.3),
827 of information. This block is preferred to the standard Packet Block
830 Packet Blocks and Simple Packet Blocks: for example, a capture tool
831 could switch from Packet Blocks to Simple Packet Blocks when the
834 The Simple Packet Block does not contain the Interface ID field.
835 Therefore, it must be assumed that all the Simple Packet Blocks have
839 Figure 6 shows the format of the Simple Packet Block.
862 | Packet Len |
865 | Packet Data |
871 Figure 6: Simple Packet Block format.
873 The Packet Block has the following fields:
875 o Packet Len: actual length of the packet when it was transmitted on
876 the network. Can be different from captured len if the packet has
879 o Packet data: the data coming from the network, including
883 The Simple Packet Block does not contain the timestamp because this
888 The Simple Packet Block is very efficient in term of disk space: a
1148 useful when reading data, but that it is not really needed for packet
1260 5.1 Other Packet Blocks (experimental)
1262 Can some other packet blocks (besides the two described in the
1346 Blocks (normally Packet Blocks or Simple Packet Blocks), of wihich it
1400 o table with position and length of any indexed packet (N entries)
1491 Simple Packet Blocks. In the most complex case, it can be used as a
