| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Simplify the detection of OpenSSL libcrypto, based on Marc Abramowitz
commit c4b7e5f2b287ee3d1de8f706b809a8e217720c4e
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Cast the pointers to uintptr_t; use AC_TYPE_UINTPTR_T to get uintptr_t
defined on older platforms that don't define it themselves.
|
| |
|
|
| |
Fixes GitHub issue #437.
|
| | |
|
| | |
|
| |
|
|
| |
Clean up a const issue while we're at it.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
If it's less than the length of the IP payload, use it as the size of
the UDP packet. If it's greater than the length of the IP payload,
and we're not dissecting the payload, report the length as bad.
|
| |
|
|
|
|
|
|
| |
Running out of packet length before running out of unreachable
destinations is an error; report it as such.
Don't worry about leftover data past the end of the list of unreachable
destinations.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Use ND_TCHECK() rather than home-brew bounds checks. Do simpler length
checks.
Let i be the length of the actual remaining packet data; use ND_TCHECK()
inside loops that iterate over the remaining data.
Let the printers for particular message types cast the raw data pointer
to a pointer of the appropriate type, rather than passing two pointers,
with different types, to the same data.
|
| |
|
|
|
|
|
|
| |
Have "struct aodv_rerr" just be the header, not including the actual
destinations.
Simplify the logic somewhat, and make it similar in the print routines
for the three types of error messages.
|
| |
|
|
|
|
|
|
|
| |
Fetch the type field without using a structure, and check to make sure
it's not past the end of the packet.
Pass to each dissection routine a pointer to the appropriate message
type structure, rather than a pointer to a union of all the message type
structures.
|
| |
|
|
|
|
|
| |
Don't run past the end of the captured data, and don't run past the end
of the packet (i.e., don't make the length variable go negative).
Also, stop dissecting if the message length isn't valid.
|
| | |
|
| | |
|
| |
|
|
| |
checksum isn't used until it's set later.
|
| |
|
|
| |
v is set to p later in a loop, and isn't used until then.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Also give more details on shell metacharacters in filter expressions -
in particular, note that a common use of a shell metacharacter is a
backslash used to escape protocol names, e.g. "ether proto \ip", and
that the alternative to quoting the entire expression is to escapet he
shell metacharacters, e.g.
tcpdump ether proto \\ip
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RFC 1119 says
Peer Poll Interval (peer.ppoll, pkt.ppoll): This is a signed
integer indicating the minimum interval between messages
sent by the peer, in seconds as a power of two. For
instance, a alue of six indicates a minimum interval of 64
seconds.
so print both the raw value and 2^{raw value}, showing the latter.
Patch from Debian bug 686276.
Reviewed-By: Guy Harris <guy@alum.mit.edu>
|
| | |
|
| |
|
|
|
|
| |
Use strtol() and only treat the argument as a number if it's *all*
number, so that interface names such as 192_1_2 aren't treated as
"interface number 192".
|
| |
|
|
|
|
|
|
|
|
|
| |
NAME_MAX is the maximum length of a file pathname *component*; PATH_MAX
is the maximum length of a file pathname. We're dealing with pathnames,
so use PATH_MAX. (On some systems, NAME_MAX can be as low as 14,
presumably for binary compatibility with V7-era data structures
containing file names, as there are probably few if any non-historic
UN*Xes around with 14-character file name limitations.)
Boost the default PATH_MAX to 1024 while we're at it.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The LLDP printer doesn't show the packet protocol unless -v is used,
which results in pretty useless output lines where only the timestamp is
present. Make sure we include the default protocol+length output even in
default mode.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Some routines return -1 on error; bail and return -1 if they do.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Make sure we don't run past the end of a BGP attribute or LDP TLV when
dissecting the attribute/TLV.
Make some of the code do a bit more of a "step the pointer through the
data"-style dissection; that was done while debugging the changes in
question. It also fixes up some code to not check for more data than
should actually be there.
Update references to RFC 4906 from the draft, and note that RFC 4447
replaces it.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Found by Xavier Heiny.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Do *NOT* assume that "%l[doxu]x" - or "%ll[doxu]" - is the way to print
a 64-bit quantity; on UN*X, it might be a "long" or a "long long",
depending on whether you're on a 32-bit or 64-bit platform and, on
Windows with MSVC++, it's not a long (even in 64-bit mode) and doesn't
use "%ll[doxu]", either. Instead, use PRI[doxu]64; that's what C99
defines, and what we define ourselves if the C environment doesn't
define it.
|
| | |
|
| | |
|
| | |
|
| | |
|
