| #
c46af893 |
| 03-Mar-2025 |
Jose Luis Duran <jlduran@FreeBSD.org> |
tests: Require python3 when using Scapy
python3 is a symbolic link that points to the current python 3.X
version.
It is possible for a system to have python (python 3.X) without the
python3 (symlin
tests: Require python3 when using Scapy
python3 is a symbolic link that points to the current python 3.X
version.
It is possible for a system to have python (python 3.X) without the
python3 (symlink) package.
Test scripts that use Scapy are invoked using python3, so add it as a
required program.
Reviewed by: ngie, asomers
Approved by: emaste (mentor)
Differential Revision: https://reviews.freebsd.org/D49007
show more ...
|
|
Revision tags: release/14.2.0-p2, release/14.1.0-p8, release/13.4.0-p4, release/14.1.0-p7, release/14.2.0-p1, release/13.4.0-p3, release/14.2.0, release/13.4.0 |
|
| #
d154dc21 |
| 26-Aug-2024 |
Kristof Provost <kp@FreeBSD.org> |
pf tests: ensure that neighbour discovery works as expected
Also check repeated calls.
MFC after: 1 week
Sponsored by: Rubicon Communications, LLC ("Netgate")
|
| #
89f67232 |
| 14-Aug-2024 |
Kristof Provost <kp@FreeBSD.org> |
pf: invert direction for inner icmp state lookups
(e.g. traceroute with icmp)
ok henning, jsing
Also extend the test case to cover this scenario.
PR: 280701
Obtained from: OpenBSD
MFC after: 1 we
pf: invert direction for inner icmp state lookups
(e.g. traceroute with icmp)
ok henning, jsing
Also extend the test case to cover this scenario.
PR: 280701
Obtained from: OpenBSD
MFC after: 1 week
Sponsored by: Rubicon Communications, LLC ("Netgate")
show more ...
|
| #
34063cb7 |
| 12-Aug-2024 |
Kristof Provost <kp@FreeBSD.org> |
pf tests: ensure that traceroutes using ICMP work
PR: 280701
MFC after: 1 week
Sponsored by: Rubicon Communications, LLC ("Netgate")
|
| #
b9f0dbc3 |
| 09-Jul-2024 |
Kristof Provost <kp@FreeBSD.org> |
pf tests: ensure we don't confuse different ICMP types
When creating a state for ICMP (v4 or v6) packets we only used the ID, which
means that we could confuse different ICMP types. For example, if
pf tests: ensure we don't confuse different ICMP types
When creating a state for ICMP (v4 or v6) packets we only used the ID, which
means that we could confuse different ICMP types. For example, if we allowed
neighbour discovery but not ICMPv6 echo requests an ND packet could create a
state that the echo request would match.
Test that this is now fixed.
Reported by: Enrico Bassetti <e.bassetti@tudelft.nl>
MFC after: 1 day
Sponsored by: Rubicon Communications, LLC ("Netgate")
show more ...
|