I have checked in with @sharpd, he mentioned that it might not be supported to use v4 nexthop for v6 route.
From local testing:
vova | ip r default via 192.168.0.1 dev wlp4s0 proto dhcp metric 600 192.168.0.0/24 dev wlp4s0 proto kernel scope link src 192.168.0.102 metric 600
PR for subtask bug merged:
https://github.com/vyos/vyos1x-config/pull/24
PR for this task will follow the update/rebuild of libvyosconfig.
In T6140#180451, @dongjunbo wrote:The Root Cause is this 'Static routes not working with PPPoE and VyOS 1.4'
https://forum.vyos.io/t/static-routes-not-working-with-pppoe-and-vyos-1-4/14102I
Does the problem only appear after your 5am reboot every day?
The Root Cause is this 'Static routes not working with PPPoE and VyOS 1.4'
https://forum.vyos.io/t/static-routes-not-working-with-pppoe-and-vyos-1-4/14102
This likely because the global state policy being reintroduced was not accounted for in the firewall check in conf script. I'll check this week.
We have something like this already for !in! interfaces:
At least tech-support-archive.tgz MUST not copied between updates
PR https://github.com/vyos/vyos-1x/pull/3155
set service config-sync secondary address 192.0.2.1 set service config-sync secondary timeout 3600
yeah I had this problem too, also @Viacheslav I think you are right:
The fix for values containing single backslashes has been merged for 1.5 in
https://github.com/vyos/vyos1x-config/pull/23
https://github.com/vyos/vyos-1x/pull/3035
As discussed, this will wait before being backported to 1.4.