https://github.com/vyos/vyos-build/pull/612

Migration requires the config file to be in the standard syntax, such as produced by the system itself (set/del; commit; save) --- in this case, a configuration that can be loaded and saved on VyOS 1.3.5 would not be missing braces as above. If one needs to hand edit a config file, at the very least one needs to load/save on the source system before migration. The only weird corner case, linked above, is when a change of mac address triggers a rewrite by the ealry-legacy parser (only used in <= 1.3.x, and only in one remaining place in 1.3.x: vyatta_interface_rescan) --- that does produce incorrect syntax and is a known problem as described in the comment in T5611; that case is also restored by saving the config on the source image before system update and the resulting migration on reboot.

I've tested and now is working correctly :

add documentation : https://github.com/vyos/vyos-documentation/pull/1444

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

This would be a great feature to have. I ran into this the other day and found out via slack single-quotes works, but only for a one-liner. ex. set route-target vpn import '65000:1 65000:2'.

This will be possible after subtask T6006, for 1.5; backport can be considered at that time, but for now limit tags to Circinus.

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

Maybe we should change firewall priority, and make sure all interfaces are defined in the system before loading firewall?

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

Sorry for the noise - see workaround

I'm re-opening until we make a final decision

See details and explanation in subtask T6327; notably, one can configure as system console, but setting at boot has limited use.

The service webproxy is deprecated and will be removed in 1.5

It can be handy to have the option to have it disabled (or you can just in bash-mode do "apt-get remove intel-microcode --purge" if you dont want it after install) but it should be enabled by default due to security reasons.

Please consider making the microcode updates optional, and possible to load a specified file downloaded separately from the CPU vendor, independent of VyOS updates.
Some possible edge cases:

• running VyOS in a VM (microcode update has no effect in the guest anyway, needs to be done in the hypervisor)
• microcode update released in a hurry breaks something, need to revert to an older one
• microcode update reduces performance, doesn't improve security of VyOS (because it's not a typical multi-user system with untrusted users who can run any programs)
• microcode update has important fixes, but it will take time before a new LTS is released, or VyOS can't be updated because the subscription has expired

I think this was resolved at some point, but I ended up removing it (the accept-protocol stuff) from my config since it didn't appear necessary and was causing issues, so I'm not certain.

set policy local-route doesn't make sense to me to have a geoip network group, however geoip in set policy route allows for greater flexibility while performing routing to ensure traffic traverse through specific destination for compliance and regulatory purposes.

@alainlamar can you check my PR https://github.com/vyos/vyos-1x/pull/3430 ?

Behavior change for this issue was fix some month ago in migration scripts, in order to remain action "return" when upgrading from older versions to new syntax.

Note that the work in the link above, but for the get_commit_schedule function itself, has already been added in subtasks T6319/T6146. As mentioned above, the get_commit_schedule function is not useful (and potentially misleading) until we replace the legacy commit algorithm in 1.5. Remove 1.4.0 tag.

speed test info: