This capture file triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
With a previous fix (3f1c4af001),
the problem no longer exists.
The pcap file was updated to pass the sanity checks and to avoid
pcap_loop() error messages.
Update the output of the test accordingly.
Partial update from 4846b3c5d0
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
With a previous update (511915bef7),
the problem no longer exists.
Thus no fix needed.
The pcap file was renamed from pcapng to pcap because it is.
Update the output of the test accordingly.
Partial update from 83a412a527
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
With some previous updates, the problem no longer exists.
Thus no fix needed.
The pcap file was updated to pass the sanity checks and to avoid
pcap_loop() error messages.
Update the output of the test accordingly.
Partial update from 13d52e9c0e
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
With the new GET_ macros, the problem no longer exists.
Thus no fix needed.
The pcap file was updated to avoid pcap_loop() error messages.
It was rename from pcapng to pcap because it is.
Update the output of the test accordingly.
Partial update from d750527684
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
With a bounds check previously added, the problem no longer exists.
Thus no fix needed.
The pcap file was updated to avoid pcap_loop() error messages.
It was rename from pcapng to pcap because it is.
Update the output of the test accordingly.
Partial update from e01c9bf767
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
With the new GET_ macros, the problem no longer exists.
Thus no fix needed.
The pcap file was updated to pass the sanity checks, keep only the
relevant packets and avoid pcap_loop() error messages.
Update the output of the test accordingly.
Partial update from d97e942237
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
With the new GET_ macros, the problem no longer exists.
Thus no fix needed.
The pcap file was updated to pass the sanity checks and to avoid
pcap_loop() error messages.
Update the output of the test accordingly.
Partial update from a152aebfd1
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
With a length check previously added, the problem no longer exists.
Thus no fix needed.
The pcap file was updated to pass the sanity checks and to avoid
pcap_loop() error messages.
Update the output of the test accordingly.
Partial update from e3f3b445e2
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
With a length check previously added, the problem no longer exists.
Thus no fix needed.
The pcap file was updated to pass the sanity checks and to avoid
pcap_loop() error messages.
Update the output of the test accordingly.
Partial update from 86326e880d
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
With the new GET_ macros, the problem no longer exists.
Thus no fix needed.
The pcap file was updated to avoid pcap_loop() error messages.
Update the output of the test accordingly.
Partial update from 3de07c7721
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
With the new GET_ macros, the problem no longer exists.
Thus no fix needed.
The pcap file was updated to pass the sanity checks and to avoid
pcap_loop() error messages.
Update the output of the test accordingly.
Partial update from bea2686c29
in 4.9 branch.
These capture files triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
With the new GET_ macros, the problem no longer exists.
Thus no fix needed.
The pcap files were updated to avoid pcap_loop() error messages.
Update the output of the tests accordingly.
Partial update from 1a1bce0526
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
fixed in the 4.9.3 release.
With the new GET_ macros, the problem no longer exists.
Thus no fix needed.
The pcap file was updated to avoid pcap_loop() error messages.
Update the output of the test accordingly.
Partial update from aa5c6b710d
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
and was fixed in the 4.9.3 release.
With the new GET_ macros, the problem no longer exists.
Thus no fix needed.
The pcap file was updated to pass the sanity checks and avoid
pcap_loop() error messages.
Update the output of the test accordingly.
Partial update from 396e94ff55
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
and was fixed in the 4.9.3 release.
It was fixed in master branch by commit
4154778a26.
The pcap file was updated to pass the sanity checks, keep only the
relevant packets and avoid pcap_loop() error messages.
Update the output of the test accordingly.
Partial update from c24922e692
in 4.9 branch.
This capture file triggered a buffer over-read with the 4.9.2 release
and was fixed in the 4.9.3 release.
With the new GET_ macros, the problem no longer exists.
Thus no fix needed.
The pcap file was updated to pass the sanity checks and to avoid
pcap_loop() error messages.
Update the output of the test accordingly.
Partial update from aa3e54f594
in 4.9 branch.
Put back the bfd_port_values, and use it to distinguish
between destination ports for RFC5883 multihop and
RFC7310 lag sessions. (The destination port is the only
difference between these messages.)
MEDSA (which unofficially stands for Marvell EDSA) relies on the
unregistered 0xDADA ethertype value that was randomly choosen and
currently used by the kernel. But with EDSA this value is programmable,
hence can be changed anytime.
Now that a reliable DLT parser is implemented for both DSA and EDSA
tagged master interfaces, let's get rid for the MEDSA ethertype parser.
The checksum calculation for IPv6 packets is based on a pseudo
header that includes the packet's final Destination Address (DA).
If the IPv6 packet contains a Routing header, the final DA is the
last element of the Routing header [RFC8200].
Currently, tcpdump supports Routing header types 0 and 2.
IPv6 Segment Routing Header (SRH) is a new Routing header type (4).
SRH is defined in draft-ietf-6man-segment-routing-header [1].
This patch fix the checksum calculation for SRv6 packets. It allows
tcpdump to get the final DA value from SRv6 packets.
[1] https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-17
The errors were:
print-ppp.c:518:9: runtime error: unsigned integer overflow: 38 - 230
cannot be represented in type 'unsigned int'
print-ppp.c:1138:63: runtime error: unsigned integer overflow: 204 - 220
cannot be represented in type 'unsigned int'
Add a test case.
The error was:
print-nfs.c:537:2: runtime error: unsigned integer overflow:
4294967295 + 3 cannot be represented in type 'unsigned int'
print-nfs.c:541:14: runtime error: unsigned integer overflow:
4294967295 + 3 cannot be represented in type 'unsigned int'
Add a test case.
This fix an undefined behavior at runtime.
The error was:
print-ipx.c:93:43: runtime error: unsigned integer overflow: 29 - 30
cannot be represented in type 'unsigned int'
Add a test case.
1) RIPv2
The error was:
print-rip.c:386:9: runtime error: unsigned integer overflow: 16 - 20
cannot be represented in type 'unsigned int'
Without this change the unsigned integer variable 'len' is assigned a
very high value, because of underflow, and the loop continue incorrectly.
Add a test case.
2) RIPv1
Same bugfix, based on a code inspection, so comes without a test case.
