Sorry, but I dont think this is fixed; I just attempted to upgrade my working 1.2.8 configuration to 1.3.

VyOS 1.4-rolling-202201041316 - works well.

Ran some quick tests with current vyos installed in a VM and a client ubuntu server VM hooked up to it - since this is all internal stuff it is a double NAT scenario with the vyos external IP allocated out of 192.168.x.x space and using 10.100.100.0/24 internally for the client ubuntu VM.

@aohanian I got it, thanks, so it doesn't delete the previous route in one commit
it can be archived with 2 commits

configure
delete protocols static route 1.1.1.1/32 dhcp-interface eth4
commit
set protocols static route 1.1.1.1/32 dhcp-interface eth5
commit

The problem in 1.3.0 is that if you delete the next-hop and then use a different next-hop, both next-hops are in the routing table. The next-hop that you deleted is still there:

I think there is a bit of confusion here. nowadays 1.4 it's works as you mention , but 1.3 doesn't remove static (so we can see both static in the RIB) . however, In my personal opinion , it should show both static in our cli (same also on FRR) , because it's possible that you may need a different prefix ,it'll be installed with a different next-hop .

@fernando What do you want to see it that case?
In the our CLI DHCP-route can be as a single value now:

set protocols static route 192.0.2.192/32 dhcp-interface 'eth0'
set protocols static route 192.0.2.192/32 dhcp-interface 'eth2'

I.e. the first route will be replaced with the second route in CLI.
So if I understand correctly you expect that this route will be also replaced an in the FRR?

For 1.4 this feature was added in T2683

Fixed in 1.3

vyos@r4:~$ show interfaces counters 
Interface    Rx Packets   Rx Bytes     Tx Packets   Tx Bytes
dum0                  0          0              0          0
eth0                126       9952             76      10316
eth1                  4        280              5        523
eth2                 37       1924              0          0
lo                    6        300              6        300
vyos@r4:~$ 
vyos@r4:~$ clear interfaces ethernet eth1 counters 
Clearing eth1
vyos@r4:~$ show interfaces counters 
Interface    Rx Packets   Rx Bytes     Tx Packets   Tx Bytes
dum0                  0          0              0          0
eth0                182      14550            108      14340
eth1                  0          0              0          0
eth2                 42       2184              0          0
lo                    6        300              6        300
vyos@r4:~$

PR https://github.com/vyos/vyatta-conntrack/pull/7

@jack9603301 Could you test it, also create a pr for the documentation?

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

@jestabro you are right. Adding no_tag_node_value_mangle=True will fix this issue.
https://github.com/vyos/vyos-1x/blob/ec13cac66ba612ecc36053158c7517c8fe993547/src/system/keepalived-fifo.py#L73-L74

self.vrrp_config_dict = conf.get_config_dict(base,
                                     key_mangling=('-', '_'), get_first_key=True,
                                     no_tag_node_value_mangle=True)

Found the problem here - I used a different and simpler version of the configuration above and *show openvpn server* returns an output when a client is connected.

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

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

PR for op-mode https://github.com/vyos/vyos-1x/pull/1204

Thanks - works again

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

Adding this issue to this task: https://forum.vyos.io/t/firewall-configuration-issue-after-upgrade/8414

PR https://github.com/vyos/vyos-1x/pull/1200
Fix for telegraf template/scripts for services.

I've used for these tests (VyOS 1.4-rolling-202202010836)
The same situation in general when you want to use "!".
Bad exampels.

set nat source rule 10 destination port !1-5
set nat source rule 10 destination port !22
set nat source rule 10 destination port !http
set nat source rule 10 destination port telnet,!http,!123,1001-1005
set nat source rule 10 destination port telnet,http,!123,1001-1005

( VyOS 1.4-rolling-202202010836)- Rule name which starts with a number work well.

docs: https://github.com/vyos/vyos-documentation/pull/707

I have found the following links:

tested my previous code in latest rolling, looking good so far.
no errors on commiting.

Seems like this is already handled in T4101

Is there any Linux implementation?

reverted broken commit

reverted commit