Okay, I can reproduce the error with an errant copy-paste; not sure how that happened in the reported lines, but if I paste the url as the image name, the resulting error matches. I will leave open for the submitter's response/comments, but otherwise close as 'invalid'.

That is an odd one: I am not able to reproduce with those 1.5-rolling versions, but will raise priority for investigation.

Changes applied

XDP was dropped
The task is not an actual

PR https://github.com/vyos/vyos-user-utils/pull/12

PR
https://github.com/vyos/vyos-1x/pull/2893

Same results here. If I remove the routes and re-add them they work perfectly. The issue only comes up at reboot.

I have another result

vyos@r1# set protocols static route 203.0.113.22/32 dhcp-interface eth2
[edit]
vyos@r1# commit
[edit]
vyos@r1# 
[edit]
vyos@r1# vtysh -c "show run" | match 203.0.113
ip route 203.0.113.22/32 192.168.100.1 eth2
[edit]
vyos@r1#

@c-po This would be the commits from https://gitlab.isc.org/isc-projects/dhcp/-/merge_requests/67 and 2 of mine to fix the issues with that PR, plus add support for ARPHRD_NONE

PR for policy https://github.com/vyos/vyos-1x/pull/2890
PR for traffic-policy https://github.com/vyos/vyos-1x/pull/2892

WLB is another feature and not related to protocols failover route

I've made mistake while configuring my test stand so the WLB in my GNS3 was affected by contrack on host machine.
Looks like the WLB works as it should.
Sorry to bother you!

Issue is back in 1.4.0-rc3

Update:
It is completely different issue

Sorry about that. I have updated the description.

Found task named wan load balance issues with 3 or more WANs.

BTW, do you have any plans to use this mechanism for WAN failover?
Could you explain or send some examples?

@devon Could you share the example of "set" commands before migration?
It is a good practice to have "set" of commands. It makes the lives of developers easy and is one of the requirements of creating bug reports.
Thanks.

In T1237#174506, @Harliff wrote:

BTW, do you have any plans to use this mechanism for WAN failover?

Is it OK to discuss such topics here?

BTW, do you have any plans to use this mechanism for WAN failover?

Could you check it? Available in the latest rolling release

Can you share your patch?

Digging into it a little, @c-po mentioned in Slack about trying https://gitlab.isc.org/isc-projects/dhcp/-/merge_requests/67 (the stalled PR). I had to fix a few things which I left as a comment on that PR just in case some else stumbles on it.

Pr for 1.5: https://github.com/vyos/vyos-1x/pull/2887

Related?

https://github.com/vyos/vyos-1x/pull/2884

Also, issues with the input

vyos@r4# set firewall ipv4 input filter rule 10 action accept
[edit]
vyos@r4# set firewall ipv4 input filter rule 10 ipsec match-ipsec
[edit]
vyos@r4# 
[edit]
vyos@r4# commit
[ firewall ]
Failed to apply firewall: /run/nftables.conf:19:17-27: Error: No such
file or directory; did you mean table ‘vyos_filter’ in family ip? delete
table ip vyos_filter                 ^^^^^^^^^^^
/run/nftables.conf:47:18-28: Error: No such file or directory; did you
mean table ‘vyos_filter’ in family ip? delete table ip6 vyos_filter
^^^^^^^^^^^ /run/nftables.conf:75:21-31: Error: No such file or
directory; did you mean table ‘vyos_filter’ in family ip? delete table
bridge vyos_filter                     ^^^^^^^^^^^

PR https://github.com/vyos/vyos-1x/pull/2883