make sure to include tcpdump-stdinc.h; it is required
added some comments about ndo functions
Merge branch 'master' of git+ssh://bpf.tcpdump.org/tcpdump/master/git/tcpdump
note changes
Merge branch 'master' of git+ssh://bpf.tcpdump.org/tcpdump/master/git/tcpdump
merge bootp.h into print-bootp.c
Print checksum in hex, and print the actual checksum, plus cleanup
Check for TLV length too small.

The TLV length includes the T and the L, so it must be at least 4.

This means we don't need the "avoid infinite loop" check later; that
check was wrong, as per GitHub issue #401 and #402; this fixes #402,
which has a different patch for that bug.
Merge pull request #403 from superjamie/cdp-checksum-and-cleanup

Print CDP checksum in hex, print the actual checksum, cleanup
Merge git://github.com/the-tcpdump-group/tcpdump
Qualify "length" when printing it.

In the "the TLV length is too short" message, we're printing the length
of the entire TLV; report it as "TLV length".  If we pass that test,
we've subtracted out the lengths of the T and the L, leaving only the
length of the V, so report it as "value length".
Update to reflect the output format changes and bug fixes for CDP.
Use tabs consistently.
Add TLV length checks, fix another length check.
More #defines for CDP lengths and offsets.
Update a URL.
Clean up configure check for libsmi.

First, check for smi.h.  If we don't have it, don't check for anything
else.

If we do have it, check for libsmi containing smiInit.  If we don't have
it, don't check for anything else.

If we do have it, check, with our test program, whether we can use it.

If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI.  Otherwise,
don't do either of those.

Check, in source, *only* for USE_LIBSMI.  If it's set, use libsmi,
otherwise don't - don't even include smi.h, even if we happened to have
found it, and don't print the libsmi version string.
Document --with-sandbox-capsicum.
Print square brackets around the tag value in RADIUS strings

Before, VLAN attributes that had a tag 1 looked like this:

  Tunnel Medium Attribute (65), length: 6, Value: Tag[1]802
  Tunnel Private Group Attribute (81), length: 4, Value: Tag 14

With the Tunnel-Medium-Type attribute (65), it is clear where the tag ends and the value begins. With this patch, the value for a string type (like Tunnel-Private-Group-Id) looks similar:

  Tunnel Private Group Attribute (81), length: 4, Value: Tag[1]4
comma in AC_MSG_ERROR confuses configure