| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | | |
This reverts commit 5ed759e023e20831a675d1432e12b08061ab1d08.
|
| |\ \
| | | |
| | | | |
Print attributes from NFLOG message
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
print MARK,PREFIX attributes
print HOOK,UID,GID,IFINDEX_INDEV,IFINDEX_OUTDEV,
IFINDEX_PHYSINDEV,IFINDEX_PHYSOUTDEV attributes if -v
print HWHEADER attributes if -vv
print other attributes w/o decode if -vvv
Аdding nflog_print.pcap for testing
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This implements "IEEE 802.3/Ethernet" mode as described in annex F of
the PTP standard. This uses the same format packets, but directly over
Ethernet instead of encapsulated in UDP.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Probably a copy & paste error.
Moreover:
Add some missing commas in output.
Fix some typos.
Update the output of a test accordingly.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A new version of MPTCP protocol (RFC8684) has been published, with some
changes to the MP_CAPABLE options handling. Let tcpdump print the protocol
version, and adjust parsing of MP_CAPABLE options according to RFC8684.
Signed-off-by: Davide Caratti <dcaratti@redhat.com>
|
| |\ \ \
| | | | |
| | | | | |
Parse the IS-IS Instance Identifier TLV from RFC8202
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This test seems to work even with "x87" floating point; perhaps it fails
on, e.g., SPARC with some compiler.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
"Normal" is what you'll get with most versions of most instruction sets;
"x87" is what you'll get with code compiled for 32-bit x86 without SSE,
using the x87 instructions, at least with some compilers.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It's All Very Complicated, so mirror what print-lmp.c does - just do a
calculation based on a particular input value and print the result using
the same format print-lmp.c does, and have tests/TESTrun see what that
result is.
Just do that inside tcpdump.c, so we don't need the fptype stuff.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add a --fp-type flag to tcpdump, which causes it to do a floating-point
operation and, based on the result of the operation, prints out
"FPTYPE{n}", where {n} is a number indicating the result.
Have tests/TESTrun run "./tcpdump --fp-type" and set a HAVE_ key based
on that. Run some tests only for FPTYPE1.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I can't seem to make those issues pop up on my (x86-64) machine, and, if
they do show up on any platforms, the best hack to handle it is probably
to have a special tcpdump flag to force it to do a floating-point
calculation and see what result is generated, and report the result, so
we know what it'll do with the numbers in the test files, and have
tests/TESTrun run tcpdump with that flag.
If those tests *do* fail, we'll know what calculations to do.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If we're skipping a test because something *is* set, say "XXX set".
If we're skipping a test because something *isn't* set, say "XXX not
set".
(Don't say the same thing in both cases.)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove a stray .md file and restore some comments from the removed .sh
files so future folk can see where the conditional tests come from, not
just the mere fact of their existence. Remove the unused fragile shebang
from testfuncs.pm.
[skip ci]
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Once we've gotten rid of those scripts, this should no longer be
necessary.
Fixes the problem I mentioned in my comment in GitHub issue #820.
Get rid of extra blank lines at the end while we're at it.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Create the tests/.passed and tests/.failed files used by test shell
scripts; once we've gotten rid of those scripts, this should no longer
be necessary.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Some script interpreters do not have the same pathname in all operating
systems where they work (e.g. Perl is /usr/local/bin/perl on FreeBSD).
Apply the classic solution to this classic problem.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
situations
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Replace calls to ipaddr_string()/ip6addr_string() with calls to
GET_IPADDR_STRING()/GET_IP6ADDR_STRING() macros performing bounds
checking.
Fix a regression in 78a4ee82226a3fe19981841dfe24d5e9cb437524.
This fixes a buffer over-read in ldp_tlv_print() discovered by
Jason Xiaole.
Add a test using the capture file supplied by the reporter updated
to keep only the packet showing the buffer over-read.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- the print routines for ptp different ptp messages
- test completed for sync message, announce message, delay request message,
delay response message and follow up message.
- integration of the ptp v2 code with the tcpdump code.
Signed-off-by: Partha S. Ghosh <psglinux@gmail.com>
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Keep track of the length of the attribute, and make sure we don't run
past it.
|
| | | |
| | | |
| | | |
| | | | |
Update the outputs of some tests accordingly.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The error were like:
print-isoclns.c:2583:20: runtime error: unsigned integer overflow:
20 - 27 cannot be represented in type 'unsigned int'
print-isoclns.c:2525:20: runtime error: unsigned integer overflow:
0 - 20 cannot be represented in type 'unsigned int'
Update the output of two tests accordingly.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These capture files triggered a buffer over-read fixed by
6f2cd8cee6372b2d3f4783ce30a603b31839d31f.
Two pcap files were updated to pass the sanity checks.
Update the outputs of the tests accordingly.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These capture files triggered a buffer over-read or a segmentation fault
with the 4.9.2 release fixed in the 4.9.3 release.
These errors were fixed in master branch by commit
daa343d8e215a6704ee37399a77a70133df51e01.
Update the outputs of the tests accordingly.
Partial update from b8f025d17f8d9d32542d21bff6dae25199761a91
in 4.9 branch.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These changes avoid some pcap_loop() errors messages like:
"tcpdump: pcap_loop: invalid packet capture length X, bigger than
snaplen of Y"
or
"tcpdump: pcap_loop: truncated dump file; tried to read X header
bytes, only got Y"
Update the output of the tests accordingly (no more "EXIT CODE" line).
Remove the no more useful .out.stderr files.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These changes avoid some pcap_loop() errors messages like:
"tcpdump: pcap_loop: invalid packet capture length X, bigger than
snaplen of Y"
or
"tcpdump: pcap_loop: truncated dump file; tried to read X captured
bytes, only got Y"
The outputs of the tests are unchanged.
Remove the no more useful -c options in the test configurations.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
There is no error.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This capture file triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
The problem was fixed in master branch by commit
09822d484b0f26d197a1ea8fdf81ca6e0d698634.
Update the output of the test accordingly.
Update from b35eb4c1630d2e40a9e25dd873c572e1aec43910
in 4.9 branch.
|