On Tue, 17 Mar 2026 11:54:30 +0100 Andrea Mayer wrote: > > @@ -819,6 +853,7 @@ test_command_or_ksft_skip ip > > test_command_or_ksft_skip ping > > test_command_or_ksft_skip sysctl > > test_command_or_ksft_skip grep > > +test_command_or_ksft_skip ip6tables > > This will skip the entire script if ip6tables is not present, which > takes down the baseline tests too. > I think a probe at startup that checks for both tunsrc support and > ip6tables would work well here. If either is missing, we can > just gracefully skip the new tunsrc tests and let the rest of the script > run as usual. > > The bottom line is that the script needs to keep working exactly as > before when tunsrc is not supported or its dependencies are missing.
FWIW that's not the general guidance for networking tests. If it's easy to handle cleanly then sure, but we should try to avoid complicating tests with workarounds for degraded environments.
