On Thu, Aug 27, 2026 at 03:07:01AM +0200, Andrea Mayer wrote:
> On Wed, 26 Aug 2026 13:49:39 +0200
> Alessio Faina <[email protected]> wrote:
>
> Hi Alessio,
>
> > I was running kernel 5.15 (5.15.0-139-generic).
> >
> > Removing the sink to /dev/null in check_hs_connectivity
> > I can see the following error:
> >
> > ------------
> > PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
> >
> > --- 10.0.0.2 ping statistics ---
> > 1 packets transmitted, 0 received, 100% packet loss, time 0ms
> >
> > TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100)
> > [FAIL]
> >
> > .....
> > ------------
> >
> > The error I can see upon installing the route in the setup is the
> > following:
> >
> > ------------
> > Error: either "to" is duplicate, or "vrftable" is a garbage.
> > ------------
>
> This error comes from the route parser: the seg6local action was
> parsed, and "vrftable" was not recognised. The End.DT4/DT6/DX4/DX6
> actions have been in iproute2 since v4.14.0, but the vrftable
> attribute only since v5.11.0.
>
> > I can see that iproute2 doesn't support any End routes
> >
> > ------------
> > ~$ ip route help 2>&1 | grep -qo "End"
> > ~$ echo $?
> > 1
> > ------------
>
> The help text reports the names of these four actions only since
> v5.14.0.
>
> > It's similar to the case we added last month(-ish) for
> > srv6_end_dt46_l3vpn_test.sh.
>
> End.DT46 was different: parsing and help line came in one commit,
> so no upstream release has one without the other.
>
> The two DX tests do not use vrftable, their seg6local routes only
> need nh4 and nh6, which are as old as the actions. Which error do
> the DX tests give on your setup?
>
> Thanks,
>
> Ciao
> Andrea
For the DX tests I was doing a local test but it's not in the original
kernel, sorry, I must have confused 2 tasks with one, so disregard the
DX4 and DX6 tests, they are not relevant to this issue; if we manage to
agree on a solution for the DT4 and DT6 tests, I will discard those
modification in a subsequent patch.
About the DT4 and DT6 tests, I thought to use the same method as the failure
was practically the same as End.DT46.
This is the version I'm currently using
ip utility, iproute2-ss200127 (should be 5.5.0 if I'm not mistaken)
and I can confirm
[SEG6_LOCAL_ACTION_END_DT4] = "End.DT4"
[SEG6_LOCAL_ACTION_END_DT6] = "End.DT6",
is available.
What do you suggest would be the right way forward to check what is
going on?
Kind regards,
-Alessio Faina
