d56f51ea7d
As part of this, we import bpf_filter.c from NetBSD. Even though that file is part of the NetBSD kernel, it is also used by userland (as is clear here). Our LWIP service has its own bpf_filter.c implementation but that implementation has certain limits (e.g. on program size) that are fine for a system service but should not apply to userland. The libpcap code has a number of blocks guarded by __NetBSD__, but none of those blocks apply to MINIX 3. In particular, some of the alignment logic used for NetBSD may in fact not work in our case. Change-Id: Ib187e22d627c929e111d5d4a991c3bee3c0154cb
28 lines
1.0 KiB
C
28 lines
1.0 KiB
C
/* $NetBSD: pcap-common.h,v 1.2 2014/11/19 19:33:30 christos Exp $ */
|
|
|
|
|
|
/*
|
|
* We use the "receiver-makes-right" approach to byte order,
|
|
* because time is at a premium when we are writing the file.
|
|
* In other words, the pcap_file_header and pcap_pkthdr,
|
|
* records are written in host byte order.
|
|
* Note that the bytes of packet data are written out in the order in
|
|
* which they were received, so multi-byte fields in packets are not
|
|
* written in host byte order, they're written in whatever order the
|
|
* sending machine put them in.
|
|
*
|
|
* ntoh[ls] aren't sufficient because we might need to swap on a big-endian
|
|
* machine (if the file was written in little-end order).
|
|
*/
|
|
#define SWAPLONG(y) \
|
|
((((y)&0xff)<<24) | (((y)&0xff00)<<8) | (((y)&0xff0000)>>8) | (((y)>>24)&0xff))
|
|
#define SWAPSHORT(y) \
|
|
( (((y)&0xff)<<8) | ((u_short)((y)&0xff00)>>8) )
|
|
|
|
extern int dlt_to_linktype(int dlt);
|
|
|
|
extern int linktype_to_dlt(int linktype);
|
|
|
|
extern void swap_pseudo_headers(int linktype, struct pcap_pkthdr *hdr,
|
|
u_char *data);
|