#
f25ceb05 |
|
19-Jun-2023 |
Kristof Provost <kp@FreeBSD.org> |
pf tests: make pfsync:defer test more robust Set the defer timeout to 2.5 seconds, and only make sure that there's at least a second of delay between the pfsync packet and the ping packet. The intent is to allow the test to pass even when there's considerable jitter on the timing measurement (e.g. when the test runs in a VM, such as during the CI tests). Allow the test to run in CI. Sponsored by: Rubicon Communications, LLC ("Netgate")
|
#
60a3a371 |
|
02-Dec-2021 |
Kristof Provost <kp@FreeBSD.org> |
pf tests: more thorough pfsync defer test Add a somewhat more extensive pfsync defer mode test. Ensure that pfsync actually delays the state creating packet until after it has sent the pfsync update and given the peer time to create the state. Ideally the test should validate the pfsync state update and generate an ack message, but to keep the test simple we rely on the timeout of the deferred packet instead. MFC after: 1 week Sponsored by: Rubicon Communications, LLC ("Netgate") Differential Revision: https://reviews.freebsd.org/D33245
|