Working on latest 1.4! 👍

Working on latest 1.4! 👍

Working on latest 1.4. 👍

It will be included after 1.4-rc2

In T5247#166517, @SrividyaA wrote:

Now we receive this error in 1.5-rolling-202312060024 when the command is executed:

vyos@R1:~$ show interfaces system
-vbash: /opt/vyatta/bin/vyatta-show-interfaces: No such file or directory

Just wanted to add that this error is also present in V1.4 RC1

Create a new feature request if you need some specific feature/features
For example, for offloads we use:

vyos@r4# set interfaces ethernet eth0 offload 
Possible completions:
   gro                  Enable Generic Receive Offload
   gso                  Enable Generic Segmentation Offload
   hw-tc-offload        Enable Hardware Flow Offload
   lro                  Enable Large Receive Offload
   rfs                  Enable Receive Flow Steering
   rps                  Enable Receive Packet Steering
   sg                   Enable Scatter-Gather
   tso                  Enable TCP Segmentation Offloading

(edited above for formatting)

I think that this should be addressed at the specific migration script:
https://github.com/vyos/vyos-1x/blob/current/src/migration-scripts/nat/5-to-6
Although there are open questions about avoiding migration, and specific ways to avoid it (boot flag 'no-vyos-migrate'), neither are the issue here: migration scripts should 'do no harm', and one invariant that can be enforced is that migration scripts should be idempotent; the above is not, as a result of:
https://github.com/vyos/vyos-1x/blob/current/src/migration-scripts/nat/5-to-6#L53-L55
I suggest the patch below to restore idempotency (which clearly can't break anything, since one would not have an empty string as inbound/outbound-interface); thoughts ?

@greywolfe You probably need to use -e without_login=true option. Could you re-check?

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.

In rVYOSONEXee494c3a1dbfca3457bcaffe89d45971348e4848#958479, @sdev wrote:

Are you able to provide the dhcp config that fails migration? I wasn't able to re-create any migration problem in my tests

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

In rVYOSONEXee494c3a1dbfca3457bcaffe89d45971348e4848#958453, @workingagain wrote:

when migrating from pre subnet-id builds to a subnet build will cause migration failed during initial startup due to missing subnet id.

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: