Don't support D-Bus sniffing on OS X.

See freedesktop.org bug 74029:

	https://bugs.freedesktop.org/show_bug.cgi?id=74029

for details.
resolve a Clang warning in can_read_linux()

./pcap-can-linux.c:246:18: warning: comparison of unsigned expression < 0 is
always false [-Wtautological-compare]
if (pkth.caplen < 0)
~~~~~~~~~~~ ^ ~
Byte-swap the T and L in TLVs as necessary when reading an NFLOG file.

That means that, when reading a LINKTYPE_NFLOG file, the type and length
values are in the byte order of the host *reading* the file, rather than
the host that *wrote* the file, just as they're in the byte order of the
host capturing the traffic if you're doing a live capture of NFLOG
messages.

That way, when reading a LINKTYPE_NFLOG file and writing another one
from those packets, the type and length in the output file will be in
the byte order of the host writing the file, rather than the byte order
of the host that wrote the input file.

Export the nflog.h file containing the declarations and definitions we
need, for use by tcpdump and other programs reading LINKTYPE_NFLOG
files.

Put the bulk of the byte-swapping code into a common routine, for use by
pcap and pcap-ng readers, while we're at it.
Have nflog_tlv_t include only the TLV header.

That way, sizeof(nflog_tlv_t) is the minimum size of a TLV.
Check caplen in the NFLOG TLV loop.

We want to process only the TLVs that are actually in the packet data,
so caplen is the right variable to use.

Also, just to make sure, check for a too-short TLV (with a length less
than the length of the TLV header), which also checks for a zero-length
TLV (which would otherwise cause an infinite loop), and put caplen and
length on the left-hand side of comparisons.
Describe all NFLOG TLV types and define structures for some of them.
Fix typo.
Remove commas from clauses in a comma-separated list.

The list of return values is a comma-separated list; if the descriptions
in that list themselves have commas, it can perhaps be confusing - does
the list item end with the comma in the description or in the comma at
the end of the description?  (The correct answer is the latter.)
update flex and GCC text in INSTALL.txt
Add {DLT,LINKTYPE}_BLUETOOTH_LINUX_MONITOR for BlueZ.

This is a new link-layer header type for the Bluetooth Linux Monitor in
the BlueZ Bluetooth stack.
Add new Bluetooth link-layer header types.
Add support for Bluetooth Linux Monitor interface

Interface "bluetooth_monitor" is used to monitoring all Bluetooth
adapters together on Linux platform.
Merge pull request #342 from MichalLabedzki/master

Add support for Bluetooth Linux Monitor interface
Check for HCI_CHANNEL_MONITOR for Linux Bluetooth Monitor support.

Support the Linux Bluetooth Monitor mechanism if:

	we support Linux Bluetooth;

	struct sockaddr_hci includes an hci_channel field;

	HCI_CHANNEL_MONITOR is defined by the Bluetooth headers;

as there are some 3.x kernel versions in which struct sockaddr_hci
includes an hci_channel field but in which HCI_CHANNEL_MONITOR is not
defined.
Add a link-layer header type for the PROFIBUS data link layer.
Do userland filtering if we can't do kernel filtering.

If, for example, the filtering doesn't pass the kernel's filter
validator because it does backward branching, as would be the case if
"ip protochain" or "ip6 protochain" were used, we don't want to fail, we
want to fall back on filtering in userland.

Use some PCAP_ERROR_ values while we're at it, to match what pcap-bpf.c
does.
Work around annoying Android problem.

For various annoying reasons having to do with DHCP software, some
versions of Android give the mobile-phone-network interface an ARPHRD_
value of ARPHRD_ETHER, even though the packet supplied by that interface
have no link-layer header, and begin with an IP header, so that the
ARPHRD_ value should be ARPHRD_NONE.

Detect those devices by checking the device name, and use DLT_RAW for them.
Pick up fix from Android libpcap.

(Did anybody ever send this fix upstream to us?)
Add support for Apple's DLT_PKTAP.
Add more details to a comment.