<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/src/migration-scripts/vrf/2-to-3, branch T6674-circ-trigger</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=T6674-circ-trigger</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=T6674-circ-trigger'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2023-08-02T09:12:23+00:00</updated>
<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>
