To reproduce, we can use the interface description
1.3.5 in config file we see \\

vyos@r1# set interfaces ethernet eth1 description 'WAN\interface'
[edit]
vyos@r1# set interfaces ethernet eth0 description 'WAN\interface'
[edit]
vyos@r1# set interfaces ethernet eth1 description 'My\LAN interface|for lan | network'
[edit]
vyos@r1# compare 
[edit interfaces ethernet eth0]
>description WAN\interface
[edit interfaces ethernet eth1]
+description "My\LAN interface|for lan | network"
[edit]
vyos@r1# commit
[edit]
vyos@r1# save
Saving configuration to '/config/config.boot'...
Done
[edit]
vyos@r1# run show conf com | match desc
set interfaces ethernet eth0 description 'WAN\\\\interface'
set interfaces ethernet eth1 description 'My\\LAN interface|for lan | network'
[edit]
vyos@r1#

After update to 1.4-rc1+

vyos@r1:~$ show conf com | match desc
set interfaces ethernet eth0 description 'WAN\\\\\\\\interface'
set interfaces ethernet eth1 description 'My\\LAN interface|for lan | network'
vyos@r1:~$

@greywolfe could you re-check? There were several fixes for ddclient.

@greywolfe Could you re-check?
If you can reproduce it, describe please in more detail, which flavor/platform/version

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

I was unable to duplicate the behavior with 1.4.0-rc1. Performed add system image https://cdn.vyos.io/1.4.0-rc1/vyos-1.4.0-rc1-amd64.iso) with above configuration, and nhrp came up on reboot. So it's common to 1.4 and 1.5, but only since sometime in December (post rc1)?

Merged

Removed

Merged

With the same config:

I think I see part of what's happening here; it looks like the format for configuration-sync URIs removed the colon (:) between the host and path:
<PROTO>://<USER>:<PASS>@<HOST>:<PATH>
is now:
<PROTO>://<USER>:<PASS>@<HOST><PATH>

It looks like what this should be converted to is as follows:

trae@cr01b-vyos# show as-path-list 
 as-path-list DAL10 {
     rule 10 {
         action permit
         description "Allow anything from or via DAL10"
>        regex 4242420668_$
     }
 }
 as-path-list IBM {
     rule 10 {
         action permit
         description "Allow anything directly from IBM Cloud"
>        regex ^_42424206(68|70)_$
     }
 }
 as-path-list INT {
     rule 10 {
         action permit
         description "Allow anything from or via int"
>        regex 4242420666_$
     }
 }

It looks like with VyOS 1.3, one way to match AS path (or at least, the way I did it) was to use an escaped parenthesis [\)], but in 1.4+ it appears this way no longer works, and instead those escapes should probably be converted to underscores (_).

I'm seeing this on 1.4 as well, dockerized build 1.4-rolling-202401061915), configured following https://docs.vyos.io/en/sagitta/configuration/vpn/dmvpn.html with no other protocols/services.

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

PR https://github.com/vyos/vyatta-op/pull/87

I haven't had the chance to test this, but the following should be sufficient to replicate the behaviour:

The best option for now would be to delete those commands and re-implement them in a separate feature request if required.
https://github.com/vyos/vyatta-op/tree/current/templates/show/remote-config

PR https://github.com/vyos/vyatta-op/pull/86

PR https://github.com/vyos/vyatta-op/pull/86

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

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

@fdcastel The thing is, we don't have secrets_lines in the dictionary.
So, it is a wholly broken script and must be deleted or rewritten.

I'm having the same error. Even with NO ipsec configured. Just using DHCP.

Can confirm, short term testing worked.

I'm seeing the same problem. Latest 1.4 version from git.

Oops, I didn't see T5647! Sorry! I guess this one can be closed as a duplicate.

In T5932#172324, @marc_s wrote:

I take it RC2 will contain these new versions @Viacheslav?

Do static addresses/gateways work stable enough?

100% agree. I have submitted a similar feature request here:

I take it RC2 will contain these new versions @Viacheslav?

Seems you're right @indrajitr:

@Viacheslav sure, updated the OP

Always use "set commands" to make it easier for developers to reproduce it.

@samip537 You should use the peer group definition inside the v6-only stanza, like so:

neighbor wg1 {                                                                                           
    interface {                                                                                          
        v6only {                                                                                         
            peer-group BACKBONE                                                                          
            remote-as 4242420669                                                                         
        }                                                                                                
    }                                                                                                    
}

@MattK provide a simple example of "set" commands to reproduce

In T5835#171322, @Viacheslav wrote:

Another bug it that /config/upnp.leases is hardcoded, but there is no script who creates it https://github.com/vyos/vyos-1x/blob/aebb458262072457c6a3840d1b17031fbd780eca/data/templates/firewall/upnpd.conf.j2#L128

It cause of

Jan 10 21:16:03 r4 miniupnpd[9869]: Reloading rules from lease file
Jan 10 21:16:03 r4 miniupnpd[9869]: could not open lease file: /config/upnp.leases