<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/src/migration-scripts/vrf/2-to-3, branch current</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=current</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=current'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2025-06-28T21:16:52+00:00</updated>
<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>T7417: check existence of table setting before return_value</title>
<updated>2025-05-05T18:50:46+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2025-05-05T18:16:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=40c82fd472c4961e506acea86461833e9b244f98'/>
<id>urn:sha1:40c82fd472c4961e506acea86461833e9b244f98</id>
<content type='text'>
Migration from 1.3.x may not contain table entries, later required.
The migration script should not fail with error, leaving enforcement to
config scripts.
</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>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>VRF: T3655: proper connection tracking for VRFs</title>
<updated>2021-07-17T19:36:39+00:00</updated>
<author>
<name>zsdc</name>
<email>taras@vyos.io</email>
</author>
<published>2021-07-12T19:59:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=22791e26f444766dc9f9e1729b72893208f58079'/>
<id>urn:sha1:22791e26f444766dc9f9e1729b72893208f58079</id>
<content type='text'>
Currently, all VRFs share the same connection tracking table, which can
lead to problems:

- traffic leaks to a wrong VRF
- improper NAT rules handling when multiple VRFs contain the same IP
networks
- stateful firewall rules issues

The commit implements connection tracking zones support. Each VRF
utilizes its own zone, so connections will never mix up.

It also adds some restrictions to VRF names and assigned table numbers,
because of nftables and conntrack requirements:

- VRF name should always start from a letter (interfaces that start from
numbers are not supported in nftables rules)
- table number must be in the 100-65535 range because conntrack supports
only 65535 zones
</content>
</entry>
</feed>
