On Mon, Mar 23, 2026 at 3:27 AM Andrea Mayer <[email protected]> wrote: > > On Fri, 20 Mar 2026 14:59:09 +0100 > Justin Iurman <[email protected]> wrote: > > > Extend srv6_hencap_red_l3vpn_test.sh to include checks for the new > > "tunsrc" feature. If there is no support for tunsrc, it silently > > falls back to the encap config without tunsrc. > > > > Cc: Shuah Khan <[email protected]> > > Cc: [email protected] > > Signed-off-by: Justin Iurman <[email protected]> > > --- > > .../net/srv6_hencap_red_l3vpn_test.sh | 95 ++++++++++++++++--- > > 1 file changed, 82 insertions(+), 13 deletions(-) > > > > Hi Justin, > > Thanks for the v4. Good job on the fallback logic. > > However, while reviewing and testing this v4 on a mixed setup (older > kernel, newer iproute2), I noticed a specific case that slips through, > unfortunately causing the baseline SRv6 tunnel tests to fail. > > Kernels that do not support tunsrc simply ignore the SEG6_IPTUNNEL_SRC > attribute. If iproute2 sends it, the kernel installs the route without > the tunsrc and returns 0 (success). As a result, check_tunsrc_support() > ends up setting HAS_TUNSRC=true and installs DROP rules that block the > baseline SRv6 traffic (please see below).
Hi Andrea, Good catch! I'll send v5 to fix the above, as well as the nits you mentioned. Thanks again, Justin
