FD.io VPP
v19.01.3-6-g70449b9b9
Vector Packet Processing
|
PCAP utility definitions. More...
Go to the source code of this file.
Data Structures | |
struct | pcap_file_header_t |
File header struct. More... | |
struct | pcap_packet_header_t |
Packet header. More... | |
struct | pcap_main_t |
PCAP main state data structure. More... | |
Macros | |
#define | foreach_vnet_pcap_packet_type |
Known libpcap encap types. More... | |
#define | foreach_pcap_file_header |
#define | foreach_pcap_packet_header |
#define | PCAP_MAIN_INIT_DONE (1 << 0) |
Enumerations | |
enum | pcap_packet_type_t { foreach_vnet_pcap_packet_type } |
PCAP utility definitions.
Definition in file pcap.h.
#define foreach_pcap_file_header |
#define foreach_pcap_packet_header |
#define foreach_vnet_pcap_packet_type |
Known libpcap encap types.
These codes end up in the pcap file header. If you decide to build a wireshark dissector, you'll need to know that these codes are mapped through the pcap_to_wtap_map[] array in .../wiretap/pcap-common.c.
For example:
{ 280, WTAP_ENCAP_VPP },
A file with the officially-allocated vpp packet type PCAP_PACKET_TYPE_vpp aka 280, will need a top-level dissector registered to deal with WTAP_ENCAP_VPP [=206].
Something like so:
dissector_add_uint("wtap_encap", WTAP_ENCAP_VPP, vpp_dissector_handle);
enum pcap_packet_type_t |