<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/src/migration-scripts/interfaces/25-to-26, branch feature/T9082-codeql-cpp</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2026-04-28T07:40:59+00:00</updated>
<entry>
<title>migration: T8280: Fix auth file read for interfaces on first boot of new image</title>
<updated>2026-04-28T07:40:59+00:00</updated>
<author>
<name>Oleksandr Kuchmystyi</name>
<email>o.kuchmystyi@vyos.io</email>
</author>
<published>2026-04-24T14:30:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=996a872eca8786ddd4335dd23dd9cb048ec11ffd'/>
<id>urn:sha1:996a872eca8786ddd4335dd23dd9cb048ec11ffd</id>
<content type='text'>
During first boot after installing a new VyOS image, migrations are
executed before the filesystem is fully initialized.
At this point `/config` is not yet bind-mounted, causing auth files
(certificates, keys, credentials) for OpenVPN, WireGuard and Ethernet
EAPoL interfaces under `/config/auth` to be inaccessible even though they
exist under the underlying `/opt/vyatta/etc/config/auth` path which is
available at all boot stages.

Add fallback logic to `read_auth_file()` to retry the file lookup under
`/opt/vyatta/etc/config/auth` when the file is not found under `/config/auth`.
</content>
</entry>
<entry>
<title>openvpn: T7738: avoid duplicate certs during 1.3 -&gt; 1.4 migration</title>
<updated>2025-12-02T06:22:18+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2025-12-02T06:14:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=63cc76fa23674aa0fe92d8fc13ba52ca1e7c98f9'/>
<id>urn:sha1:63cc76fa23674aa0fe92d8fc13ba52ca1e7c98f9</id>
<content type='text'>
When migrating from VyOS 1.3 to 1.4, OpenVPN interfaces sharing the same
certificate (chain) end up getting duplicated certificate entries, one per
interface — instead of reusing a single cert if applicable.

This change makes the migration logic detect shared certificates and reuse a
single CA and server certificate objects, preventing redundant certificate
entries in the config.
</content>
</entry>
<entry>
<title>T7591: remove copyright years from source files</title>
<updated>2025-06-28T21:16:52+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2025-06-28T18:51:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=1478516ae437f19ebeb7d6ff9b83dd74f8e76758'/>
<id>urn:sha1:1478516ae437f19ebeb7d6ff9b83dd74f8e76758</id>
<content type='text'>
The legal team says years are not necessary so we can go ahead with it, since
it will simplify backporting.

Automatically removed using: git ls-files | grep -v libvyosconfig | xargs sed -i -E \
's/^# Copyright (19|20)[0-9]{2}(-[0-9]{4})? VyOS maintainers.*/# Copyright VyOS maintainers and contributors &lt;maintainers@vyos.io&gt;/g'

In addition we will error-out during "make" if someone re-adds a legacy
copyright notice
</content>
</entry>
<entry>
<title>migration: T6007: convert all migration scripts to load as module</title>
<updated>2024-06-26T20:38:41+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2024-06-20T01:16:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=26740a8d583f64dc0a27b59dd4ae303056972c0b'/>
<id>urn:sha1:26740a8d583f64dc0a27b59dd4ae303056972c0b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>migration: T5413: re-sequence interfaces migration scripts</title>
<updated>2023-12-10T10:49:25+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-12-10T10:44:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=98ca0984312257a09b57d4aac60ff4abf7f84e66'/>
<id>urn:sha1:98ca0984312257a09b57d4aac60ff4abf7f84e66</id>
<content type='text'>
PR https://github.com/vyos/vyos-1x/pull/2540 backported a migration script from
current to the equuleus LTS branch. As migration scripts are executed in order
to adjust the CLI for necessary improvements in future LTS releases we need to
change the versioning of the migration files to match the new "base" version
from the previous LTS release.

In theory this could break very ancient 1.4 rolling releases (from the early
days of the OSPF refactoring) - but those versions are considered very much
unstable.

Now this is the last chance to sync up the migration scripts before the 1.4 LTS
release.
</content>
</entry>
<entry>
<title>T5427: Fix migration script arguments len expects 2 args</title>
<updated>2023-08-02T09:12:23+00:00</updated>
<author>
<name>Viacheslav Hletenko</name>
<email>v.gletenko@vyos.io</email>
</author>
<published>2023-08-02T09:12:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=d1923b7b58795f0d9635ae0e8df110f591881bdf'/>
<id>urn:sha1:d1923b7b58795f0d9635ae0e8df110f591881bdf</id>
<content type='text'>
The script's name is always provided as the first argument sys.argv[0]
Expected length for argv is 2 (script itself + config file)

Change: 'if (len(argv) &lt; 1)' to 'if len(argv) &lt; 2'
</content>
</entry>
<entry>
<title>pppoe: T4384: replace default-route CLI option with common CLI nodes already present for DHCP</title>
<updated>2022-04-21T20:08:38+00:00</updated>
<author>
<name>Christian Poessinger</name>
<email>christian@poessinger.com</email>
</author>
<published>2022-04-21T20:03:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=a2ab95ff68b709f7ca31006bdef6607ef4ce961d'/>
<id>urn:sha1:a2ab95ff68b709f7ca31006bdef6607ef4ce961d</id>
<content type='text'>
VyOS 1.4 still leverages PPPd internals on the CLI.

pppd supports three options for a default route, none, auto, force.
* none: No default route is installed on interface up
* auto: Default route is only installed if there is yet no default route
* force: overwrite any default route

There are several drawbacks in this design for VyOS and the users. If auto is
specified, this only counted for static default routes - but what about dynamic
ones? Same for force, only a static default route got replaced but dynamic ones
did not got taken into account.

The CLI is changed and we now re-use already existing nodes from the DHCP
interface configuration:
* no-default-route:
  On link up no default route is installed, same as the previous
  default-route none

* default-route-distance:
  We can now specify the distance of this route for the routing table on the
  system. This defaults to 210 as we have for DHCP interfaces. All this will be
  migrated using a CLI migration script.
</content>
</entry>
</feed>
