Page MenuHomeFreeBSD

pf tests: Test unicast reverse path forwarding check
ClosedPublic

Authored by kp on Feb 15 2021, 10:18 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 12 2024, 12:25 PM
Unknown Object (File)
Feb 10 2024, 9:37 PM
Unknown Object (File)
Feb 3 2024, 8:16 AM
Unknown Object (File)
Jan 11 2024, 5:25 AM
Unknown Object (File)
Dec 24 2023, 3:36 PM
Unknown Object (File)
Dec 12 2023, 5:23 AM
Unknown Object (File)
Nov 8 2023, 5:39 AM
Unknown Object (File)
Nov 4 2023, 3:01 PM

Details

Summary

Ensure that pf's urpf-failed keyword works as expected.

PR: 253479
MFC after: 1 week

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kp requested review of this revision.Feb 15 2021, 10:18 PM
melifaro added inline comments.
tests/sys/netpfil/pf/pass_block.sh
209

Nit: maybe it's worth to name the jail according to the test, like "jls_pf_urpf"?
This will allow running this test independent of others.

This revision is now accepted and ready to land.Feb 15 2021, 10:26 PM
tests/sys/netpfil/pf/pass_block.sh
209

The name of the jail is only part of the issue.

We also re-use IP ranges (because we use documentation IP ranges and there are only so many to go around), so even with different names the tests could not run in parallel.

If we want to get there it would probably make more sense to have the framework start the test in its own vnet jail. That is, we could nest the jails, and at that point the conflicting names or IP ranges wouldn't be an issue.