You can achieve this using tcprewrite (part of the tcpreplay suite):
If you control the system generating the packet captures, you can force the capture engine to record packets using an older, universally compatible link-layer type before writing to disk.
Capturing directly on eth0 , wlan0 , or enp3s0 forces the capture utility to record native Ethernet headers (DLT 1), which all analysis tools universally support. 3. Force an Older Cooked Format During Capture
Understanding the "-pcap network type 276 unknown or unsupported-" Error
So, what is number 276? According to the official pcap.h definitions and the dlt.h registry maintained by the community, DLT value 276 is often mapped to DLT_IEEE802_15_4_TAP or a vendor-specific/protocol-specific link type, depending on the build of your libpcap.
tcpdump -i eth0 -w capture.pcap
You can achieve this using tcprewrite (part of the tcpreplay suite):
If you control the system generating the packet captures, you can force the capture engine to record packets using an older, universally compatible link-layer type before writing to disk. -pcap network type 276 unknown or unsupported-
Capturing directly on eth0 , wlan0 , or enp3s0 forces the capture utility to record native Ethernet headers (DLT 1), which all analysis tools universally support. 3. Force an Older Cooked Format During Capture You can achieve this using tcprewrite (part of
Understanding the "-pcap network type 276 unknown or unsupported-" Error Force an Older Cooked Format During Capture Understanding
So, what is number 276? According to the official pcap.h definitions and the dlt.h registry maintained by the community, DLT value 276 is often mapped to DLT_IEEE802_15_4_TAP or a vendor-specific/protocol-specific link type, depending on the build of your libpcap.
tcpdump -i eth0 -w capture.pcap