VyOS 1.3 allows dots in policy object names such as route-maps and prefix-lists but later releases, including VyOS 1.4 and 1.5, introduced stricter validation requiring policy object names to contain only alphanumeric characters, hyphens, and underscores.
Example of config in 1.3.5 or 1.3.8:
set policy prefix-list 5.5.53.249-EXPORT description 'prefixes list'
After upgrading to VyOS 1.4 or 1.5, the existing configuration can no longer be committed because the object name violates the newer naming rules:
vyos@vyos:~$ conf
WARNING: There was a config error on boot: saving the configuration now could overwrite data.
You may want to check and reload the boot config
[edit]
vyos@vyos# load
Loading configuration from 'config.boot'
Load complete. Use 'commit' to make changes effective.
[edit]
vyos@vyos# compare
+ policy {
+ prefix-list 5.5.53.249-EXPORT {
+ description "test"
+ rule 10 {
+ action "permit"
+ prefix "5.5.53.0/24"
+ }
+ rule 20 {
+ action "permit"
+ prefix "5.5.50.0/24"
+ }
+ rule 30 {
+ action "deny"
+ prefix "5.5.0.0/24"
+ }
+ }
+ }
[edit]
vyos@vyos# commit
[ policy prefix-list 5.5.53.249-EXPORT ]
[ policy prefix-list 5.5.53.249-EXPORT ]
Name of prefix-list can only contain alpha-numeric letters, hyphen and underscores
[[policy]] failed
Commit failedThis can result in a migration failure or leave the upgraded system with a configuration that cannot be committed.
Request to replace unsupported characters ( . , +) with _ when migrating from 1.3.x and handle name collisions safely to prevent commit failures.